Blockchain RPC access for AI agents — 200+ networks via DRPC MCP gateway
Two tools with TypeBox schemas and descriptions present, but significant gaps in parameter documentation and output schema clarity. drpc_setup has a reasonable description (145 chars) and one optional parameter with description. drpc_coinbase_wallet_setup has good description (156 chars) but zero parameters, limiting composability. Neither tool documents return structure for LLM planning. Parameter descriptions exist but lack format/constraint details (e.g., what constitutes a valid API key format?). No error handling guidance for LLMs on recovery paths. Tool names follow verb_noun pattern (positive), but lack clarity on when to use each vs. the other.
Install/configure Coinbase Agentic Wallet / Payments MCP in ~/.pi/agent/mcp.json for pi-mcp-adapter. Creates ~/.payments-mcp/bundle.js via npx @coinbase/payments-mcp when missing.
Bootstrap DRPC access for Pi. With apiKey, configure DRPC MCP. Without apiKey, install/configure Coinbase Payments MCP so the agent can acquire a DRPC key via secure x402 without private keys in Pi.
Output schemas not documented. LLMs cannot plan downstream tool calls or extract required fields (configPath, bundlePath, url). Both tools return structured objects with 'content' and 'details' but this is never declared in tool definitions.
drpc_coinbase_wallet_setup has zero parameters (empty Type.Object({})), making it non-composable. If an agent needs to configure Coinbase payments with custom options (e.g., specific bundle path, config location), this tool cannot accept them. Reduces flexibility.
Parameter 'apiKey' description lacks format constraints. Does it accept raw keys, full URLs, or both? The description mentions 'https://lb.drpc.org/mcp/...' but does not specify the regex pattern or length limits. LLMs may pass invalid formats.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
Error handling provides no recovery guidance. If configureDrpc() or ensureCoinbasePaymentsBundle() throws, the LLM receives a raw error message with no actionable next steps (e.g., 'Try calling X first' or 'This is retryable'). Violates recovery-guide pattern.
Tool descriptions do not clarify when to use drpc_setup vs. drpc_coinbase_wallet_setup. An LLM may call both or the wrong one. Descriptions should state: 'Use drpc_setup to configure DRPC directly (requires API key). Use drpc_coinbase_wallet_setup to bootstrap Coinbase Payments MCP for x402 key acquisition.'