get_planning_benchmark — WealthSchema MCP Tool Read-only
get_planning_benchmark
(get planning benchmark) is one of 8 tools on the
WealthSchema
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_planning_benchmark from your client
- Claude Code WealthSchema get_planning_benchmark run in your project directory
- Claude Desktop WealthSchema get_planning_benchmark ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WealthSchema get_planning_benchmark ~/.cursor/mcp.json
- VS Code WealthSchema get_planning_benchmark .vscode/mcp.json
- Zed WealthSchema get_planning_benchmark ~/.config/zed/settings.json
- Windsurf WealthSchema get_planning_benchmark ~/.codeium/windsurf/mcp_config.json
- Cline WealthSchema get_planning_benchmark ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WealthSchema get_planning_benchmark ~/.gemini/settings.json
- Grok WealthSchema get_planning_benchmark .mcp.json (in your project root)
- ChatGPT WealthSchema get_planning_benchmark Settings → Connectors → Advanced → Developer mode
- Claude.ai WealthSchema get_planning_benchmark Settings → Connectors → Add custom connector
- LangChain WealthSchema get_planning_benchmark pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://www.wealthschema.com/api/mcp
Other 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.