Fetch a Yahoo Finance quote for a stock symbol and get normalized quote fields in clean JSON, making it easy to retrieve current market data for a ticker.
Yahoo Finance ticker quote. Returns normalized fast quote fields for one Yahoo Finance symbol.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Yahoo Finance symbol such as AAPL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, yet description fails to disclose behavioral traits such as rate limits, data freshness, response structure, or error handling. Merely stating 'returns normalized fast quote fields' is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise single sentence with no redundant text. Could benefit from more structured information, but compression is efficient for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description should provide more detail on the response content. 'Normalized fast quote fields' is vague; typical fields like price, change, volume are missing, leaving the agent with insufficient context to interpret results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (parameter 'symbol' has description). Description adds no additional semantic value beyond what the schema already provides, meeting the baseline but not exceeding it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it returns normalized fast quote fields for one symbol. However, it doesn't contrast with sibling tools like yahoo_finance_ticker_info, leaving some ambiguity about what specific data is included.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. The word 'fast' hints at use case but does not provide clear directives or comparisons.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.