A Model Context Protocol server for querying stock price information from the Polygon.io API
Single tool with adequate but incomplete definition quality. Tool name 'get_stock_price' follows verb_noun convention and is clear. Description exists but is minimal (54 chars, below the 194 char baseline average). Input schema is present with proper JSON Schema structure and type declarations. However, critical gaps exist: the 'date' parameter is marked as required in the schema registration but the description says 'optional', this is a dangerous inconsistency that will confuse LLMs and cause validation failures. No output schema is documented, forcing LLMs to infer response structure. Error handling returns generic API errors without actionable guidance for recovery. No resource/context about what the tool returns or how it chains with other potential tools.
Get stock price information for a specific symbol
Required vs optional parameter mismatch: 'date' is marked required in ListToolsRequestSchema but described as optional. Schema says required=['symbol','date'] but description says '(optional, defaults to latest)'. This will cause LLM validation failures when the parameter is omitted.
Tool description too brief (54 chars; baseline is 194 chars). Lacks context on WHEN to use this tool, WHAT to expect from the response, prerequisites, or how it relates to the resource endpoint that also returns stock data. LLMs need 10 - 1024 character descriptions with explicit intent guidance.
No output schema documentation. Tool returns a JSON object with fields (symbol, price, open, high, low, volume, timestamp) but there is no declared schema for the response. LLMs cannot plan chaining or extract data without knowing the response structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 47 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 40 | - | v1 |
Error handling returns unstructured error messages without recovery guidance. When Polygon API fails, the tool returns 'Polygon API error: <message>' with no suggestion for next steps (retry, try alternative endpoint, check input format). Pattern 'recovery-guide' requires: 'User not found. Try search_users() with a partial name.'
Parameter descriptions lack format constraints. 'date' says 'YYYY-MM-DD format' but provides no validation guidance or examples of valid/invalid input. The tool will silently fail if the LLM passes a date in a different format, with no clear error message telling the LLM what went wrong.
Duplicate endpoints: both a Resource (stock://AAPL/current) and a Tool (get_stock_price) return similar data but with different interfaces. Unclear to LLMs which to use when. No documentation distinguishes the use case for each (e.g., 'Use resource for real-time AAPL only; use tool for any symbol or historical dates').