Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_splits

Fetch stock split events for a Yahoo Finance symbol, returning each split's Unix timestamp and ratio, plus dividends and capital gains data.

Instructions

Yahoo Finance splits. Returns the stock split events for a Yahoo Finance symbol such as AAPL, each with a Unix timestamp and a split ratio such as 4:1. The response object also has dividends and capital_gains fields.

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 full behavioral burden. It helpfully discloses the return shape (each event has a Unix timestamp and a ratio like '4:1') and notes extra response fields, but says nothing about permissions, rate limits, or behavior when no splits exist.

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 short sentences that are front-loaded with the core purpose before describing the return shape. Efficient, though the final sentence about dividends/capital_gains fields is slightly tangential to a splits tool.

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?

With no output schema, the description usefully sketches the return shape, which is the right thing to cover. It is adequate for a simple one-parameter tool but leaves open questions about symbol format strictness, empty-result behavior, and how the dividends/capital_gains fields relate to the dedicated sibling tools.

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 the single `symbol` parameter is already documented. The description only adds an example value (`AAPL`) that duplicates the schema's own example, contributing little beyond what the structured field provides — 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 and resource ('Returns the stock split events') for a Yahoo Finance symbol, which an agent can distinguish from generic finance lookups. However, it does not name or differentiate itself from close siblings like yahoo_finance_ticker_dividends or yahoo_finance_ticker_actions, leaving the boundary implicit.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative sibling is named. The only usage signal is the implicit fact that it returns splits, which the agent must infer from the purpose statement.

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