Find trending Yahoo Finance symbols for a given region to track market interest and popular assets; set the count to limit results.
Yahoo Finance trending symbols. Returns trending Yahoo Finance symbols for a region.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Symbol count | |
| region | Yes | Region such as US |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the function without revealing traits like data freshness, pagination, or limitations. This 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?
The description is concise, consisting of two short sentences that convey the essential purpose. It is front-loaded and avoids unnecessary words, though it could be slightly more structured.
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 the tool's simplicity (2 parameters, no output schema), the description is minimally adequate for purpose but lacks important context about behavior, usage, and output format. It is incomplete for informed agent selection.
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?
The input schema has 100% description coverage for both parameters (region and count). The description does not add any additional meaning beyond the schema, so it meets the baseline but adds no value.
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 the tool returns trending Yahoo Finance symbols for a region, which is specific and distinguishes it from other yahoo_finance tools like search or screener. However, it could be more precise about what 'trending' means (e.g., most active, gainers).
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 is provided on when to use this tool versus alternatives such as yahoo_finance_market_summary, yahoo_finance_search, or other trending tools. The description lacks context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.