Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_shares_full

Fetch historical shares-outstanding data for a Yahoo Finance symbol to track share count changes over time, with optional start and end dates.

Instructions

Yahoo Finance historical share counts. Returns the historical shares-outstanding series for a Yahoo Finance symbol. start and end accept YYYY-MM-DD, RFC3339 or Unix seconds; without them the last 18 months are returned. Each point has timestamp, datetime and shares_out.

Input Schema

NameRequiredDescriptionDefault
endNoEnd date as YYYY-MM-DD, RFC3339, or Unix seconds
startNoStart date as YYYY-MM-DD, RFC3339, or Unix seconds
symbolYesYahoo Finance symbol such as AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does useful work: it discloses the default behavior (last 18 months when start/end are omitted) and the shape of each returned point (timestamp, datetime, shares_out). It omits any statement about permissions or rate limits, but for a read-only data fetch the key behavioral facts are covered.

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?

Three tight sentences with no waste; the core purpose is front-loaded before the parameter and return details. Minor redundancy with the schema's date-format description, but nothing is padded.

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?

With no output schema, the description usefully covers the return shape itself, and the default time window is spelled out. Complete enough for a 3-parameter read tool, though it never addresses how the output is paged or ordered.

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 schema already documents symbol and the accepted date formats. The description repeats the format list but adds one genuine piece of meaning beyond the schema: the 18-month default when start/end are absent. 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+resource: returns the historical shares-outstanding series for a Yahoo Finance symbol. An agent knows exactly what data comes back. It does not, however, distinguish itself from the sibling yahoo_finance_ticker_shares, so the 'full' vs non-full distinction is left unexplained.

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?

Usage is implied by the phrasing 'historical share counts' and the default 18-month window, but there is no explicit when-to-use or when-not-to-use guidance, and the near-identical sibling yahoo_finance_ticker_shares is never mentioned as an alternative.

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