report_outcome — AgentBuffs MCP Tool
report_outcome
(report outcome) is one of 4 tools on the
AgentBuffs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call report_outcome from your client
- Claude Code AgentBuffs report_outcome run in your project directory
- Claude Desktop AgentBuffs report_outcome ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentBuffs report_outcome ~/.cursor/mcp.json
- VS Code AgentBuffs report_outcome .vscode/mcp.json
- Zed AgentBuffs report_outcome ~/.config/zed/settings.json
- Windsurf AgentBuffs report_outcome ~/.codeium/windsurf/mcp_config.json
- Cline AgentBuffs report_outcome ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentBuffs report_outcome ~/.gemini/settings.json
- Grok AgentBuffs report_outcome .mcp.json (in your project root)
- ChatGPT AgentBuffs report_outcome Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentBuffs report_outcome Settings → Connectors → Add custom connector
- LangChain AgentBuffs report_outcome pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentbuffs https://agentbuffs.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 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.