MCP server that exposes BTC Direct API operations as tools, handling client authentication and proxying requests to the BTC Direct API
Single tool 'dynamic_openapi_operations' has critical structural issues. Tool name lacks action verb (should be 'execute_openapi_operation' or similar). Description is generic and does not explain WHEN to use this tool vs direct API calls. Input schema exists but is severely underspecified: 'parameters' field is described as 'Dynamic parameters based on the specific operation', this is circular and provides zero guidance to LLMs about what values are valid. No output schema documented. The tool conflates multiple concerns (parameter mapping, request body handling, response parsing) into one opaque operation. Code shows token management and auth injection, but these implementation details are invisible in the tool definition, leaving LLMs unable to reason about prerequisites or side effects.
Dynamically generated tools from OpenAPI specification. Each operation in the OpenAPI spec becomes a tool with inputs mapped from parameters and request body, and outputs mapped from success responses.
Tool name 'dynamic_openapi_operations' does not start with an action verb. LLMs cannot infer intent from the name alone. Should be 'execute_openapi_operation' or 'call_btc_direct_api'.
Input schema for 'parameters' field is circular and non-actionable: 'Dynamic parameters based on the specific operation'. LLMs cannot determine valid values, types, or constraints. Must enumerate actual parameters from OpenAPI spec or provide a structured schema per operation.
No output schema documented. Tool description does not specify what fields the response contains, forcing LLMs to guess about downstream field availability and breaking tool chaining.
Tool description (generic) does not explain prerequisites (authentication token must be obtained first), side effects (API calls are destructive), or when to use this tool. Lacks WHAT, WHEN, and consequence clarity required by pattern:tool-description.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 22 | 2026-07-28+ | v2 |
Single monolithic tool wraps entire OpenAPI spec. This violates single-responsibility principle (pattern:tool). Should expose individual tools per operation (e.g., 'get_account_balance', 'create_order', 'list_transactions') with explicit names, descriptions, and schemas.