Crawlora MCP

yahoo_finance_ticker_shares_full

Read-only

Fetch historical shares-outstanding rows from Yahoo Finance fundamentals time series for one symbol. Use yahoo_finance_ticker_shares for the ticker's current share statistics.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "yahoo_finance_ticker_shares_full"
  }
}

Input Schema

Name	Required	Description
`end`	No	End date as YYYY-MM-DD, RFC3339, or Unix seconds.
`start`	No	Start date as YYYY-MM-DD, RFC3339, or Unix seconds.
`symbol`	Yes	Yahoo Finance symbol such as AAPL.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description adds real context beyond that: the data is historical time-series rows from fundamentals, scoped to one symbol, which tells the agent what kind of payload to expect. It omits anything like rate limits or auth needs, but those are not critical here.

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?

Two sentences, zero filler, with the primary purpose front-loaded and the disambiguation clause second. Every sentence earns its place.

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?

An output schema exists, so return values need not be described, and the annotations cover safety. Purpose, scope, and sibling routing are all present. Only minor gap is any note on whether start/end are optional for full history, which the schema already implies.

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 description coverage is 100%, so start, end, and symbol are already documented with formats. The description adds only 'for one symbol', which is already implied by the schema's singular symbol field, so it does not meaningfully extend parameter understanding. Baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource -- 'Fetch historical shares-outstanding rows from Yahoo Finance fundamentals time series' -- and explicitly contrasts with the sibling yahoo_finance_ticker_shares. An agent can distinguish this historical time-series tool from the current-statistics sibling without opening either schema.

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

Usage Guidelines4/5

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

Names the alternative (yahoo_finance_ticker_shares) and the selecting condition (current share statistics vs. historical rows). Clear routing guidance, though it stops short of stating explicit exclusions such as when neither tool applies.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?