Loading ToolBench
MCP server for interacting with the x402 payment protocol on Solana, providing tools for service discovery, payment handling, wallet management, and documentation search
This server exhibits critical definition quality failures across nearly all tools. Tool definitions are inferred from a React component (tools-reference.tsx) rather than from actual MCP tool registration code. The source code shows Express/MCP server scaffolding but no visible tool handler implementations. No input schemas are present in the visible code, only high-level parameter names in a UI component. Descriptions range from generic to moderately helpful, but lack LLM-optimization patterns (WHEN to use, dependencies, error recovery). Critical security concern: tools like 'consume_x402_service' (WRITE operation handling payments) lack error handling guidance, confirmation patterns, and clear output schemas. No parameter-level type validation or enum constraints visible. Most tools appear to be delegating to external services (Solana, X402 facilitators) without clear response structure documentation.
Ask questions about developing on Solana with the Anchor Framework.
Search documentation across the Solana ecosystem to get the most up to date information.
A Solana expert that can answer questions about Solana development.
Consume a specific x402 service with automatic payment handling.
Retrieve a list of available facilitators.
Retrieve the public key of the configured wallet.
Tool definitions inferred from React UI component, not from actual MCP server registration code. No explicit tool handler implementations visible.
Input schemas completely absent or minimally specified. Only parameter names listed; no type definitions, constraints, or validation rules visible. Per HARD SCORING RULE, tools with no input schema get schema score of 0.
Tool naming inconsistency and poor convention: 'Ask_Solana_Anchor_Framework_Expert' and 'Solana_Expert__Ask_For_Help' use PascalCase with underscores instead of verb_noun snake_case. Names do not start with clear action verbs ('ask' buried in middle). LLMs cannot easily infer intent.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-21 | F | 44 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 12 | - | v1 |
Retrieve the USDC balance of the configured wallet.
Retrieve a list of available X402 services from the facilitator.
Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about x402, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.
Visual diagram showing the x402 protocol flow and architecture
Output schemas not documented. Tools like 'get_x402_services', 'get_wallet_public_key', 'consume_x402_service' return unspecified response structures. LLM cannot plan downstream calls or extract required fields. Violates pattern:tool requirement for documented return types.
WRITE operation 'consume_x402_service' handles financial transactions (payments) with no visible error handling, confirmation pattern, or recovery guidance. No dry-run mode. Violates pattern:confirmation-request and pattern:error-classification.
Parameter descriptions are minimal or generic. No guidance on format, constraints, or dependencies. E.g., 'facilitatorUrl' has description 'The URL of the X402 facilitator to query (By default your facilitator url', incomplete sentence, no constraint info, no examples. Does not meet 10 - 1024 char requirement for actionable descriptions.
No error handling guidance visible. Tools that call external APIs (Solana, X402 facilitators) provide no recovery hints. E.g., 'consume_x402_service' fails silently, does it return a structured error, HTTP status, or exception? No pattern:recovery-guide implementation.
Vague tool names for delegation tools. 'Ask_Solana_Anchor_Framework_Expert' and 'Solana_Expert__Ask_For_Help' appear to delegate to external LLM services. No clarity on what differentiates them or when to use which. Single 'ask_solana_expert' tool would be clearer.