Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_holders

Retrieve Yahoo Finance holder data for a stock symbol, including major holder breakdown, institutional ownership, fund holders, and insider holders.

Instructions

Yahoo Finance holders. Returns holder data for a Yahoo Finance symbol such as AAPL, under modules: the major holders breakdown (majorHoldersBreakdown), institutional ownership, and the fund and insider holder modules.

Input Schema

NameRequiredDescriptionDefault
symbolYesYahoo Finance symbol such as AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden, but it does add value by disclosing the return structure: majorHoldersBreakdown, institutional ownership, and fund/insider holder modules. It omits any mention of auth needs, rate limits, or data freshness, which for an unannotated tool is a gap.

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

Conciseness4/5

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

A single front-loaded sentence with no wasted words, leading with the verb and resource before the parameter detail. Slightly dense in its module enumeration but still efficient.

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

Completeness3/5

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

For a simple one-parameter read tool with no output schema, naming the returned module categories is useful, but the description doesn't clarify what each module actually contains or how the holder breakdown is structured. Adequate but with room to do more.

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?

With one parameter at 100% schema coverage, the schema already documents `symbol`. The description only echoes the example ('such as AAPL') without adding format or validity constraints, so baseline 3 is appropriate.

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?

States a specific verb ('Returns holder data') and resource ('Yahoo Finance holders') tied to a `symbol`, and enumerates the module categories returned. It is clear what the tool does, though it does not explicitly contrast with siblings like yahoo_finance_ticker_funds or sec_institutional_holdings.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites, and no alternatives. It only notes that a Yahoo Finance symbol is required, leaving the agent to infer when holders data is preferable to related tools.

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