# Debugging agent messages and "invalid tool call" **URL:** \ **Category:** Pebble Index\ **Created:** [August 19, 2026, 8:01am UTC](https://forum.repebble.com/t/debugging-agent-messages-and-invalid-tool-call/1406 "2026-08-19T08:01:16Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![filling-waking-gem](https://avatars.discourse-cdn.com/v4/letter/f/ecd19e/32.png) [@filling-waking-gem](https://forum.repebble.com/u/filling-waking-gem)\ **Post date:** [August 19, 2026, 8:01am UTC](https://forum.repebble.com/t/debugging-agent-messages-and-invalid-tool-call/1406/1 "2026-08-19T08:01:16Z")
MCP is awesome but also tricky. Right now if anything goes wrong I can get the log of back and forth between my client and the pebble cloud agent, but i can’t figure out how to see the agent’s reasoning, what tool it tried to call, or what failure actually occurred. Was it an authentication issue? Service failure? Malformed request? Dropped session? Is there a way to dig into further debugging detail than the “trace timeline” and the ring sync inspector’s GenericFailure? ---
**Author:** ![eric](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/eric/32/239_2.png) [@eric](https://forum.repebble.com/u/eric)\ **Post date:** [August 19, 2026, 2:03pm UTC](https://forum.repebble.com/t/debugging-agent-messages-and-invalid-tool-call/1406/2 "2026-08-19T14:03:47Z")
If you tap the share icon in the new bug report screen, you can download logs from the Pebble app. It’s not perfect right now. We’ll definitely add better MCP analysis but that might help in the short term! ---
**Author:** ![filling-waking-gem](https://avatars.discourse-cdn.com/v4/letter/f/ecd19e/32.png) [@filling-waking-gem](https://forum.repebble.com/u/filling-waking-gem)\ **Post date:** [August 20, 2026, 5:12am UTC](https://forum.repebble.com/t/debugging-agent-messages-and-invalid-tool-call/1406/3 "2026-08-20T05:12:53Z")
Thanks fpr the tip @eric! Unrortunately the zipped logs don’t clarify what tool was called, why, or what the error was. I’d submit a pr but those parts are server side… ---
**Author:** ![filling-waking-gem](https://avatars.discourse-cdn.com/v4/letter/f/ecd19e/32.png) [@filling-waking-gem](https://forum.repebble.com/u/filling-waking-gem)\ **Post date:** [August 21, 2026, 11:28pm UTC](https://forum.repebble.com/t/debugging-agent-messages-and-invalid-tool-call/1406/4 "2026-08-21T23:28:07Z")
See [Validate mcp server name will survive composite tool name round-trip by ohthehugemanatee · Pull Request #367 · coredevices/mobileapp · GitHub](https://github.com/coredevices/mobileapp/pull/367) for the issue and my patch to resolve it. In the meantime, users beware: if your MCP server “name” has spaces or special characters, the agent receives the wrong MCP name to call and it fails. Stick with alphanumeric and “-” and it’ll work. ---
**Author:** ![filling-waking-gem](https://avatars.discourse-cdn.com/v4/letter/f/ecd19e/32.png) [@filling-waking-gem](https://forum.repebble.com/u/filling-waking-gem)\ **Post date:** [August 26, 2026, 7:50pm UTC](https://forum.repebble.com/t/debugging-agent-messages-and-invalid-tool-call/1406/5 "2026-08-26T19:50:13Z")
… and I just put 2 and 2 together about which @eric answered my post. You’re doing fantastic work, thank you for all of it. The best part of the Index experience so far has been the sense that this device is so open because your team really cares about users, you understand that flexibility surfaces the best use cases, and genuinely welcome that feedback/contribution. It’s refreshing in the age of narrative, and I know it doesn’t happen by accident. Thank you! ---
**Author:** ![eric](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/eric/32/239_2.png) [@eric](https://forum.repebble.com/u/eric)\ **Post date:** [August 26, 2026, 8:51pm UTC](https://forum.repebble.com/t/debugging-agent-messages-and-invalid-tool-call/1406/6 "2026-08-26T20:51:43Z")
Thanks so much for the PR. We’ll check it out. I appreciate your note as well. Remember that today’s day one. It’s just going to get better!