analyze_tool_call — Agent Utility MCP MCP Tool
analyze_tool_call
(analyze tool call) is one of 4 tools on the
Agent Utility MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_tool_call from your client
- Claude Code Agent Utility MCP analyze_tool_call run in your project directory
- Claude Desktop Agent Utility MCP analyze_tool_call ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Utility MCP analyze_tool_call ~/.cursor/mcp.json
- VS Code Agent Utility MCP analyze_tool_call .vscode/mcp.json
- Zed Agent Utility MCP analyze_tool_call ~/.config/zed/settings.json
- Windsurf Agent Utility MCP analyze_tool_call ~/.codeium/windsurf/mcp_config.json
- Cline Agent Utility MCP analyze_tool_call ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Utility MCP analyze_tool_call ~/.gemini/settings.json
- Grok Agent Utility MCP analyze_tool_call .mcp.json (in your project root)
- ChatGPT Agent Utility MCP analyze_tool_call Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Utility MCP analyze_tool_call Settings → Connectors → Add custom connector
- LangChain Agent Utility MCP analyze_tool_call pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-utility-mcp https://agent-utility-mcp.insivotron.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.