Skip to content

Troubleshooting

While we’ve taken steps to ensure the smoothest experience possible, you may encounter the following issues in the beta release.

“Could not connect to MCP Server [server name]”

Section titled ““Could not connect to MCP Server [server name]””

Solutions:

  • Check to make sure your configuration aligns with the setup instructions
  • Stop generating the current response, refresh the page and try again
  • Disconnect from and reconnect to the connector
  • If neither of these work, delete the connector and add it again
  • If it still doesn’t work, contact jordan.lee@sony.com and report a bug.

Claude makes 10+ tool calls before providing an answer.

Section titled “Claude makes 10+ tool calls before providing an answer.”

Solutions:

  • Use the system prompt to refine Claude’s search approach.
  • Modify the system prompt to instruct Claude to prioritize quick answers over deep research.
  • Interrupt Claude’s response and ask it to summarize the information it found.

Solutions:

  • Disconnect from and reconnect to the connector
  • If this doesn’t work, delete the connector and add it again

Solutions:

  • Refresh the page, wait 30 seconds before making a query
  • Make your first request smaller. After successful response, resume normal operation

“Tool call [tool name] returned no results or 429 error”

Section titled ““Tool call [tool name] returned no results or 429 error””

Solutions:

  • Wait several seconds before making another request

  • If your LLM is making rapid consecutive requests, prompt it to space out tool calls

  • If the tool call body has a top_k (number of content to retrieve) greater than 5, prompt it to keep top_k < 5:

    {
    "query": "exposure compensation",
    //top_k indicates the number of results to return in the response
    "top_k": 1
    }