HyperFill MCP server provides 19 trading tools with mostly complete schemas and descriptions. Schemas are well-formed with proper types and parameter descriptions. Descriptions are present for all tools (80-240 chars, within baseline range). However, there are moderate gaps: (1) Several related tools lack clear differentiation (get_best_order, get_best_bid, get_best_ask are near-duplicates); (2) No output schemas documented for any tool, LLMs cannot plan downstream calls or extract chaining IDs; (3) Error handling is not visible in source, no recovery guidance; (4) Tool descriptions lack WHEN guidance (e.g., 'Use this to check funds before placing an order'); (5) Some parameters accept opaque values without constraints (e.g., marketName is free-form string with no enum or format hint); (6) No confirmation or dry-run pattern for destructive tools (place_limit_order, place_market_order, cancel_order, move_asset_from_vault); (7) Audit trail and permission checking not visible. Tool naming follows verb_noun convention well. Parameter naming is mostly consistent (marketName, baseAsset, quoteAsset) but inconsistent in a few cases (side enum uses 'bid'/'ask' instead of 'buy'/'sell', breaking chat convention). Average tool definition quality is solid but lacks production-grade polish and error recovery.

• Document output schemas for all tools. For example, place_limit_order should return { order_id: string, status: 'pending'|'filled'|'partial', price: string, quantity: string, timestamp: ISO8601 }. This enables downstream tool chaining.
• Consider consolidating get_best_bid and get_best_ask into a single parameterized tool (get_best_order with side param) or document why all three are necessary.
• Add confirmation/dry-run support to destructive tools. Pattern: place_limit_order(..., dry_run=true) returns 'Would place order for 100 HBAR at 0.50 USDT each. Confirm?' Then a confirm_order(order_id) tool executes.
• Add enum constraint to marketName parameter: provide list of valid markets in description or accept both 'hyperfill' and 'HyperFill' with case normalization.
• Add WHEN guidance to check_available_funds: 'Call before place_limit_order to verify sufficient balance. Returns: { asset, available_balance, locked_balance }. If available_balance < required_amount, move_asset_from_vault or wait for pending orders to settle.'
• Accept both 'bid'/'ask' and 'buy'/'sell' as side enum values, with internal normalization to bid/ask. This bridges financial jargon and chat language.
• Add bounds to numeric parameters: price (string, must be valid decimal > 0), quantity (number, 0 < quantity <= max_order_size, check get_market_overview for max_order_size).
• Implement error responses with recovery guidance. Pattern: 'Insufficient funds: need 500 USDT, available 200 USDT. Try: (1) move_asset_from_vault(500), (2) reduce quantity to 0.4 HBAR @ 0.50 USDT, (3) check_available_funds to see pending orders settling.'

Inferred effective spec: <=2025-11-25.

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