TradingAgents MCP server demonstrates consistent tool naming with proper verb-prefixes (get_*) and adequate parameter typing, but suffers from significantly incomplete descriptions and missing output schema documentation. All 10 tools follow the get_* naming convention appropriately. Parameter descriptions are present and reasonably specific (e.g., 'Stock ticker symbol', 'Current date in YYYY-MM-DD format'), meeting the baseline for 72-char average param annotation. However, tool descriptions are uniformly brief (90-140 chars), falling short of the baseline 194-char average and lacking the WHAT/WHEN/WHY clarity required by pattern:tool-description. Most critically, no tool documents its output schema or return structure, violating the hard requirement that LLMs know what fields to expect (pattern:tool, D.Schemas & Output). No error handling guidance is present. Output is read-only across all tools, but this is not explicitly stated in descriptions. The server provides no pagination documentation despite tools that likely return collections (get_news, get_global_news, get_stock_data). STDIO transport is a hard architectural constraint limiting this to tier-D status.

• Add output schema documentation to every tool. For get_fundamentals, document: 'Returns object with fields: ticker (string), pe_ratio (float), market_cap (string), dividend_yield (float), ...' Use JSON Schema in the tool definition to make it machine-parseable.
• Expand tool descriptions to 150 - 250 chars following the WHAT/WHEN/WHY pattern. E.g., 'Get comprehensive financial metrics (P/E, debt-to-equity, ROI) for a stock. Use when analyzing a company's financial health before making buy/sell recommendations. Returns latest quarterly and annual figures.'
• Add pagination documentation to get_news, get_global_news, get_stock_data: 'Results are limited to N items. Use start_date/end_date or look_back_days to narrow results. If more data is needed, narrow the date range and call again.'
• Add enum constraint to get_indicators 'indicator' parameter: {"type": "string", "enum": ["rsi", "macd", "boll", "sma", "ema", "volume"], "description": "Technical indicator to calculate. Must be one of: rsi, macd, boll, sma, ema, volume."}
• Add error recovery guidance to each tool description. E.g., 'If ticker is invalid, try get_fundamentals with a different ticker symbol. Common tickers: AAPL, NVDA, TSLA. Returns error message if data is unavailable for the date range.'
• Migrate to fastmcp with proper tool registration including return type schemas. Ensure tool definitions explicitly declare readOnlyHint: true for all tools to signal idempotency to agents.
• Clarify date handling: 'Dates must be trading days. If a weekend/holiday is passed, data from the nearest preceding trading day is returned.' Document what happens when curr_date is today vs. historical.

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

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