Tiger MCP has moderate definition quality with clear naming and reasonable parameter documentation, but lacks structured output schemas and contains several parameter completeness gaps. All 6 tools follow verb_noun naming convention (tiger_list_accounts, tiger_add_account, tiger_get_quote, tiger_get_kline, tiger_get_contracts, tiger_get_financials). Descriptions are present and reasonably detailed (100-200 chars typical). However, tool output schemas are not documented in the source code provided, only input schemas are visible. Parameter descriptions are generally present but some lack detail on constraints, formats, and valid ranges. Error handling patterns are not evident in the provided source.

• Document output schemas for all tools. Each tool needs a clear description of response structure: 'Returns an object with fields: accounts (array of {id, name, status, environment, permissions}), total_count (integer), next_cursor (string or null)'. This enables downstream chaining and reduces hallucination.
• Move api_key and secret_key out of tiger_add_account parameters. Instead, accept an optional server_url and environment, then retrieve credentials from a server-side secure store (environment variable, vault, or encrypted config). Add a separate tool like 'tiger_configure_credentials' that runs as admin-only server initialization, not as an agent-callable tool.
• Add explicit JSON Schema enum and minmax constraints. For 'period', add enum: ['1m', '5m', '15m', '30m', '1h', '2h', '4h', '1d', '1w', '1M']. For 'count', add minimum: 1, maximum: 300. For 'environment', add enum: ['sandbox', 'production'].
• Implement pagination for tiger_list_accounts. Add optional 'limit' (default 20, min 1, max 100) and 'cursor' parameters. Return response with fields: accounts (array), total_count (integer), next_cursor (string or null). Document in description: 'Results are paginated. Use limit and cursor to fetch all accounts.'
• Document error scenarios and recovery. Add to each tool's description: 'On API failure (network timeout, invalid symbol), returns error with code and retry guidance. Common errors: invalid_symbol (check symbol format), auth_failed (verify credentials are configured), rate_limited (retry with exponential backoff).'

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

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry