Single tool with excellent naming, descriptions, and output schema documentation. Tool name 'get_fear_greed_index' follows verb_noun convention and clearly signals read-only behavior. Description is comprehensive (227 chars, within 10-1024 baseline) and explains what the tool does, when to use it, and what it returns. Input schema is empty but appropriate for a parameter-free data fetch. Output schema is fully documented with Zod types and detailed field descriptions. Error handling provides actionable messages. Main limitation: tool lacks parameter validation rules and does not expose common LLM-friendly enhancements (batch operations, pagination, filtering).
Get US stock market Fear & Greed Index data. Returns comprehensive market sentiment analysis including the main composite index and 7 individual indicators (market momentum, stock price strength/breadth, options sentiment, volatility, safe haven demand, junk bond demand). Each indicator includes score (0-100), rating, and timestamp. See schema for detailed field descriptions.
Input schema is empty object {}, tool accepts no parameters, limiting composability and filtering. LLMs cannot refine queries (e.g., historical lookback, specific indicators only). Pattern suggests discovery tools should expose constrained options (e.g., time_period enum).
Output response structure mixes content array (text field with JSON stringified data) and structuredContent.data (typed object). This dual-response pattern is legacy; modern MCP tools should return only structured output. LLMs work better with pure structured responses.
No pagination or result limiting documented, even though output includes 10+ nested objects. If this data grows (e.g., extended historical series), response could bloat context. Baseline says tools returning lists should accept limit/page and return counts.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 65 | 2025-06-18+ | v2 |
| 2026-03-09 | D | 53 | - | v1 |
Error handling returns a generic error response with human-readable message, which is good. However, no guidance on recovery, e.g., 'Retry in 5 minutes' for rate limits, or 'Check network connectivity' for connection errors. Pattern suggests recovery-guide.