Hey, can you see if a fresh Composer session sorts this out?
Sometimes the LLM can get itself in a state where it doesn’t call the tools correctly, but we’re hoping to improve the stability to stop this from happening in the future!
I’m facing this issue for the last two days. I tried new composers, restarted Cursor too, but I’m still having errors calling tools. It was working before, and no code was changed. I don’t know why the error also. Is it possible to add some sort of error message?
Could you help me grab a request ID for one of these failing tool calls?
This will help us track down what’s going on:
This is probably a network/connectivity thing, but the request ID will help us know for sure
Here you go:
0cffc15e-90a2-4bc8-a878-059e5ebd9c25
c686eff3-4a1a-45ab-a237-413d790d2741
Hey, I can’t see any errors here related to tool calls.
Do you know which tool is failing?
It’s MCP tools. I had added things 3 mcp. It was working until it decided to randomly stop working. I haven’t changed any code either. And there’s no error message.
0.46 fixed this issue. No code was changed on my end, but the MCP tool calls are working again.
Hi, I’m having this issue since a couple days, it happens constantly after few prompts. Last request-id were it happened is
5050da9f-e156-4734-8cba-2d6789cf933b
I’m using cursor 0.46.4 (commit db71624816f6d52f6e54f47c37cdc7df23e22620 )
After “error calling tools” happens, any following prompt get stuck “generating”. Closing/reopening Cursor fixes the composer I was using (agent mode btw) for a few prompt, then the error reappears.
Opening a new composer session (if that’s what “cursor: new chat” does), opens a new chat immediately stuck (only restarting cursor alleviates the issue)
Same, having this issue. Restarting cursor fixes for a while, but then it suddenly happens again. Chat ID: c551eb1c-08d2-48a5-8c39-caca4345ac4f.
I got that errors again too much again in Claude 3.7 Sonnet.
Is that take my request credits every errors?
getting the same … wasted so many fast requests retrying…
I’ve been dealing with this error all day. How Do I fix it?
