Retrieve valuation measures for a stock ticker from the Yahoo Finance key statistics table. Provide a symbol such as AAPL to get available valuation data as JSON.
Yahoo Finance valuation measures. Returns the valuation table from the Yahoo Finance key statistics page when Yahoo serves the table.
| 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?
The description hints at conditional availability ('when Yahoo serves the table'), which adds some behavioral context. However, with no annotations provided, it does not disclose rate limits, data freshness, or response variability beyond the mention.
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?
Two short sentences efficiently convey the core purpose without redundancy. Could be slightly more informative but is concise.
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 one parameter and no output schema, the description is adequate but lacks detail about what the valuation table contains (e.g., market cap, enterprise value) and the output format. Leaves gaps for an agent to infer.
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% with one parameter 'symbol' described as 'Yahoo Finance symbol such as AAPL'. The description does not add extra meaning beyond the schema, meeting the baseline.
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?
The description clearly states it returns the valuation table from Yahoo Finance key statistics page, providing specific verb and resource. However, it does not differentiate from sibling tools like yahoo_finance_ticker_info or yahoo_finance_ticker_financials.
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 guidance on when to use this tool versus alternatives. Lacks context on prerequisites or scenarios where this tool is preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.