delete_custom_benchmark — agentery MCP Tool Mutating
delete_custom_benchmark
(delete custom benchmark) is one of 19 tools on the
agentery
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call delete_custom_benchmark from your client
- Claude Code agentery delete_custom_benchmark run in your project directory
- Claude Desktop agentery delete_custom_benchmark ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agentery delete_custom_benchmark ~/.cursor/mcp.json
- VS Code agentery delete_custom_benchmark .vscode/mcp.json
- Zed agentery delete_custom_benchmark ~/.config/zed/settings.json
- Windsurf agentery delete_custom_benchmark ~/.codeium/windsurf/mcp_config.json
- Cline agentery delete_custom_benchmark ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agentery delete_custom_benchmark ~/.gemini/settings.json
- Grok agentery delete_custom_benchmark .mcp.json (in your project root)
- ChatGPT agentery delete_custom_benchmark Settings → Connectors → Advanced → Developer mode
- Claude.ai agentery delete_custom_benchmark Settings → Connectors → Add custom connector
- LangChain agentery delete_custom_benchmark pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentery https://agentery.com/api/mcpOther tools on this server
- research_capability
- search_providers
- find_market
- compare_providers
- get_price_index
- price_benchmark
- get_price_index_history
- market_gaps
- suggest_alternatives
- demand_signals
- report_outcome
- rank_providers_for_workflow
- get_provider_profile
- get_provider
- market_report
- create_custom_benchmark
- get_custom_benchmark
- update_custom_benchmark
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.