MCP server for fetching stock prices using Yahoo Finance
Single tool with minimal definition quality. Tool name 'get_current_price' follows verb_noun convention (+), but description is only 16 characters in English ('获取股票的当前价格' = 'Get stock current price'), falling below the 20-char minimum threshold. Input schema is present with proper JSON Schema structure and type definitions, but parameter description '股票代码' (stock code) is generic and lacks format/constraint guidance. No output schema documented. No error handling guidance provided, the tool returns raw exception strings on failure, offering no recovery path. Tool is READ_ONLY (safe), but lacks idempotent/destructive annotations. No pagination, batching, or composition support.
获取股票的当前价格
Tool description is 16 characters (below 20-char minimum). Provides no context on when to use this tool vs alternatives, what it returns, or prerequisites.
No output schema documented. LLM cannot predict return type (string vs object vs array) or structure downstream tool calls.
Parameter 'symbol' description '股票代码' lacks format guidance. No examples, constraints, or valid value ranges (e.g., 'AAPL, 0700.HK, BTC-USD formats accepted').
Error handling returns raw exception strings ('Error: {e}'). No recovery guidance for LLM. Should categorize errors (invalid symbol, API timeout, rate limit) with actionable next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Tool lacks idempotent/readOnly annotations. While risk is marked READ_ONLY in metadata, tool definition should include toolAnnotations (readOnlyHint) for protocol clarity.