Bitkub MCP demonstrates solid foundational quality with 28 well-structured tools, clear naming conventions, and comprehensive parameter schemas. All tools follow verb_noun naming patterns (btk_get_*, btk_place_*, btk_crypto_*). Tool descriptions are present and generally informative (avg ~150 chars), explaining WHAT the tool does and WHEN to use it. However, the server exhibits several systematic gaps: (1) Parameter descriptions for optional _fields parameters across all tools are generic and repetitive ('Comma-separated list of fields to include in response'), providing minimal guidance on valid field names or use cases; (2) Output schemas are completely undocumented, no description of what fields are returned, their types, or how downstream tools should consume them; (3) Error handling guidance is absent, no recovery patterns or actionable error messages; (4) Some parameter relationships are underdocumented (e.g., btk_cancel_order requires 'id' OR 'hash' but this is stated only in description, not as a schema constraint). Despite these gaps, the server demonstrates above-average implementation quality for community MCP servers, with consistent patterns, proper type definitions, and pragmatic tool grouping. Estimated median tool score: 68/100, driven by strong naming/description but weak output documentation and error handling.

• Add outputSchema documentation to every tool. For each tool, document returned fields: {"type": "object", "properties": {"field_name": {"type": "<type>", "description": "..."}, ...}}. At minimum, document 5-10 key fields per tool. Example for btk_ticker: returns {symbol, last_price, bid, ask, percent_change, volume, high, low, timestamp}.
• Replace generic '_fields' parameter description with tool-specific guidance. For btk_ticker, change from 'Comma-separated list of fields to include in response' to 'Comma-separated list of fields to include (e.g., symbol, last_price, bid, ask, volume, percent_change). Omit to return default fields. Valid values: symbol, last_price, bid, ask, high, low, vol, percent_change, timestamp.'
• Add error recovery guidance to destructive tools. For btk_place_bid, append to description: 'On failure: check btk_wallet to verify available balance, or call btk_place_bid_test to validate parameters first.' For btk_crypto_withdraw, add: 'Destination address must be whitelisted in your Bitkub account; withdrawal cannot be reversed. Use btk_crypto_addresses to list whitelisted addresses first.'
• Enforce mutual exclusivity for 'id' vs 'hash' in btk_cancel_order and btk_order_info via explicit parameter description: 'Either id or hash must be provided, but not both. If you have the order ID, use id. If you have the order hash, use hash.'
• Add JSON Schema constraints for numeric limits. For all tools with 'lmt' parameter, add: {"lmt": {"type": "integer", "minimum": 1, "maximum": 100, "default": 10, "description": "..."}}.

Inferred effective spec: 2026-07-28+.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained