Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_industry

Fetch detailed Yahoo Finance data for one industry key, including overview, parent sector, top companies, growth leaders, and research reports to support sector analysis.

Instructions

Yahoo Finance industry detail. Returns Yahoo Finance detail for one industry key such as semiconductors: name, overview, its parent sector (sector_key, sector_name), top companies, top performing companies, top growth companies and research reports. Valid keys come from /yahoo-finance/industries.

Input Schema

NameRequiredDescriptionDefault
keyYesIndustry key such as semiconductors

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It discloses the return fields and key source, which is useful, but it does not mention read-only behavior, error handling for invalid keys, rate limits, or any other operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and compact: it identifies the tool, lists the returned data, and states where valid keys come from in two sentences. Every clause contributes useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter retrieval tool with no output schema and no annotations, the description provides enough context to invoke it correctly: it names the required key, gives an example, and enumerates the response sections. Deeper response structure is not specified, but the key operational details are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the single `key` parameter is already documented in the schema. The description adds the example 'semiconductors' and the valid-key source endpoint, but this is a modest addition beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific retrieval action and resource ('Yahoo Finance detail for one industry key') and enumerates the returned content, making the tool's purpose clear. It does not explicitly name sibling tools, but the industry-vs-sector distinction is implicit in the parent-sector field.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by noting that valid keys come from `/yahoo-finance/industries`, but it does not explicitly say to call that endpoint first or when to prefer this over yahoo_finance_sector. The agent can infer the lookup flow, but alternatives are not spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools