Skip to content
APIAgent-ready

MCP tool calls answer a timeout error after 30 seconds

A tool call on the MCP endpoint that runs past 30 seconds is now stopped and answered with a JSON-RPC timeout error that says to retry, instead of the connection ending with no answer.

Each tools/call on https://api.last-price.ai/api/mcp/rpc has 30 seconds. Before, a call that ran longer could end with the connection closing and no reply, and over a stream the stream simply stopped, so your agent could not tell what happened.

Now a call still running at 30 seconds is stopped and answered at once with a JSON-RPC error:

  • error.code is -32001, the request timeout code of the MCP reference SDK, and id is your request's own id.
  • error.data holds code: "upstream_timeout", retryable: true, timeout_ms: 30000, the tool name, a hint, and an empty next.
  • Over a stream, the error is the response event and the stream then closes normally.

What to do: send the same call again once. If it times out again, wait a minute before retrying. Work already under way when a call is stopped may still finish, so a timed-out compute_price can still be counted. Calls that finish in time see no change, and every other tool failure is still a result with isError: true. The locally run MCP server applies the same rule, with the limit configurable through LASTPRICE_TIMEOUT_MS. Questions: support@last-price.ai.