Retrieve a list of Yahoo Finance industry keys to query the industry endpoint. Use these keys to access structured industry data for financial analysis.
Yahoo Finance industries. Lists Yahoo Finance industry keys that can be queried with the industry endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description simply says it lists keys. With no annotations, the description carries full burden for behavioral disclosure. It does not mention that the data is read-only, how fresh the data is, or any other behavioral traits (e.g., no side effects). This is minimal transparency.
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 extremely concise: two short sentences that convey the purpose and an important usage hint. No unnecessary words.
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?
For a simple list tool with no parameters and no output schema, the description is adequate but could be more complete. It does not mention the format of the keys, whether the list is static or dynamic, or any ordering. However, it provides enough for basic usage.
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 zero parameters, and schema description coverage is 100% (empty). The description adds no parameter information because there are none. Baseline of 3 is appropriate as no additional meaning is needed.
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's purpose: listing Yahoo Finance industry keys. It uses a specific verb ('lists') and resource ('Yahoo Finance industry keys'), and distinguishes itself from sibling tools like yahoo_finance_industry (which likely requires a key) and yahoo_finance_sectors.
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?
The description indicates that the output can be used with 'the industry endpoint', implying yahoo_finance_industry. This provides context for when to use this tool (before querying a specific industry). However, it does not explicitly mention alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.