Skip to main content

First, identify the outcome

For HTTP, check the status code and response body. For MCP, check result.isError and result.structuredContent.error as well: HTTP success does not prove tool success.

Fix the reported problem

Retry without starting duplicate work

If the network disconnects before a response arrives, the search may still have started. Retry the same request with its original key, or retrieve the operation if you already have its ID. Do not switch keys simply because the browser or client stopped waiting. Once an operation is terminal, replaying its key does not restart it. Correct invalid inputs or wait for the reported allowance reset before deliberately starting new work. API keys on one subscription share limits; rotating keys does not create extra allowance.

Check MCP separately

If the assistant cannot list tools, follow the MCP connection checks. If it can list tools but a search fails, the transport may be working: inspect the tool’s structured error, subscription, and request key. Connecting to Mintlify’s documentation-search MCP does not connect the assistant to Jolts’ authenticated company-data tools.

Verify the recovery

Repeat a corrected request and inspect the full result. For background work, continue until the operation finishes, fails, or expires. Check the evidence and coverage before using a returned company in a sales decision. If it still fails, share the operation ID and error code with support, not credentials or an unredacted request dump.