Loading ToolBench
A multi-service MCP gateway and code-mode agent system for Cloudflare Workers that enables contract-first planning and execution of tool workflows
This is a gateway/specification server, not a functional MCP server. It exposes OpenAPI specs via HTTP but does NOT implement the MCP protocol itself. The three tools (products, fx, cart-intel) are defined only as metadata entries in spec-index.ts with minimal descriptions. No input schemas are visible in the source, only parameter names and types are listed in the evaluation summary, not in actual JSON Schema format. The server is a specification aggregator for downstream tools, not an MCP tool provider. Tool descriptions are generic (10-60 chars) and lack actionable context. No error handling, no output schema documentation, no parameter validation guidance.
Cart and shortlist analysis tool.
Exchange-rate retrieval tool for price normalization.
Public product catalog and trending product retrieval tool.
No input schemas visible in source code. Tool definitions in spec-index.ts contain only metadata (key, name, version, description); actual JSON Schema definitions are not shown. Cannot verify parameter types, constraints, or required fields.
Descriptions are too short and lack actionable context. 'Public product catalog and trending product retrieval tool' (60 chars) does not explain WHEN to use it, what it returns, or how it differs from similar tools. Baseline for A+ tools is 50-200 chars with clear intent.
Tool names lack clear action verbs. 'products', 'fx', and 'cart-intel' are nouns, not verb_noun patterns (e.g., 'list_products', 'get_exchange_rates', 'analyze_cart'). LLMs cannot infer intent from noun-only names.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 27 | 2026-07-28+ | v2 |
No output schema documentation. The evaluation summary lists input parameters but provides no information about what these tools return, what fields are in the response, or how downstream tools should consume the output.
This is a specification gateway, not an MCP server. It serves OpenAPI specs via HTTP but does not implement the MCP protocol (no tools/call, resources/read, prompts/get endpoints). It cannot be used as an MCP server directly.