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 for a Yahoo Finance ticker using symbol and optional date range to track share count changes over time.

Instructions

Yahoo Finance historical share counts. Returns historical shares-out rows from Yahoo fundamentals timeseries.

Input Schema

TableJSON 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

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It states the return data but provides no behavioral details such as data freshness, authentication requirements, rate limits, or error behavior. The agent is left uninformed about side effects or 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?

Two concise sentences front-load the core purpose. Every sentence provides essential information without redundancy.

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

Completeness2/5

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

The tool is relatively simple but lacks output schema. The description fails to cover data format, supported date ranges, or limitations. Given the financial domain, more detail on data scope would improve completeness.

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 baseline is 3. The description adds minimal value beyond schema descriptions, e.g., 'historical shares-out rows' confirms data type but no further semantic context.

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?

The description clearly states the resource ('Yahoo Finance historical share counts') and the action ('Returns historical shares-out rows'). It distinguishes from sibling tools by specifying the exact data type and source.

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?

No guidance on when to use this tool versus alternatives (e.g., yahoo_finance_ticker_shares). No exclusions or prerequisites mentioned, leaving the agent to infer usage context.

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