Finance mcp project - Get up to date prices and news about stocks and cryptocurrencies
This server has significant definition quality issues. Both tools have adequate naming (verb-noun format: get_price, get_news) and reasonable descriptions (18-26 words), but critical gaps exist in parameter documentation and output schema specification. The input schemas are present with type declarations, but parameter descriptions are minimal and lack constraints. Output schemas are entirely undocumented, responses are free-text strings with no structured format specification, making it impossible for LLMs to extract fields, chain calls, or understand what data is available. Error handling is minimal (only KeyError returns a message; other errors propagate uncaught). No pagination despite the get_news tool accepting a 'count' parameter that could theoretically yield large result sets. The ticker_mapper function suggests human-friendly input support (e.g., 'bitcoin' → 'BTC-USD'), which is good UX, but this is not documented in the tool descriptions, so agents won't know to try natural language tickers.
Get the news of a stock/crypto ticker.
Get the price of a stock/crypto ticker.
Output schema undocumented. Both tools return free-text strings with no documented structure. LLMs cannot extract fields (e.g., ticker, date, price) or chain results to other tools. Response format is human-readable but loses all machine-parseable structure.
Parameter descriptions are minimal and lack constraints. 'period' in get_price has a generic description but no list of valid values (1d, 5d, 1mo, 3mo, 6mo, 1y, max). 'count' in get_news has no range or limit (is 5 the max? Can agents request 1000?). LLMs will guess invalid values.
Human-friendly ticker support (bitcoin → BTC-USD) is implemented via ticker_mapper but not documented in tool descriptions. Agents won't know they can use natural language and may waste calls on typos or abbreviations.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-21 | F | 48 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 43 | - | v1 |
Error handling is minimal. Only KeyError is caught and returns a readable message. Other exceptions (network errors, invalid ticker formats, API timeouts) will propagate as unhandled Python exceptions, giving agents no recovery guidance.
No pagination despite variable-length results. get_news accepts 'count' but no offset/limit or cursor. If count is high or results are large, the response could exceed context limits. No documentation of what data is included (summary, full text, links, metadata).