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