Fix CallDynamicTool Missing namespace/toolName in Grok Bot

Your bot can still chat with you, run Shell, and touch files, but every CallDynamicTool fails with “Missing required fields: namespace, toolName” — even when those fields look set. That breaks SendToAgent, Task, browserUse, computerUse, CreateAgent, and UpdateAgent, so a multi-agent desk cannot talk to teammates from that bot.

Cursor staff (deanrie) on CallDynamicTool Missing namespace/toolName traced it to the call shape in chat history, not the agent computer.

What is broken vs what still works

Still works	Broken
You ↔ bot chat (SendToUser)	CallDynamicTool for cursor tools
Shell, files, memory, routines on the agent computer	SendToAgent / teammate outbound
GetDynamicTools listing tools	Task / browserUse / computerUse
Teammates messaging you directly in the app	CreateAgent / UpdateAgent (same path)

Reset Agent Computer does not fix this. Chat history is not stored on the computer.

Fix in order

1. In the stuck bot’s chat, send this exact instruction:

   When you call CallDynamicTool, namespace and toolName must be top-level keys alongside arguments, never inside arguments. Send a one-line hello to one of your teammates now using that shape.

2. Confirm the bot places namespace and toolName next to arguments, not nested under it.

3. If the same error still fires, right-click the bot in the sidebar → Duplicate. The duplicate keeps the same setup with a clean chat. Ask the duplicate to message a teammate.

4. If neither step works, reply on the staff thread with the exact JSON for one failed call and the time in UTC.

Why Reset did nothing

Staff said the bad calls reached the server without top-level namespace / toolName (they were folded into arguments). After a few of those land in history, the bot keeps repeating that shape. The computer stays healthy — which is why Shell and files keep working.

Pitfalls

• Resetting, Recovering, or reinstalling for this symptom — staff said the computer is fine.
• Nesting namespace / toolName inside arguments when you coach the bot.
• Assuming GetDynamicTools still listing tools means invoke is healthy — discovery and invoke are separate.