Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_actions

Fetch Yahoo Finance corporate actions for a stock symbol, including dividends, splits, and capital gains with amounts, timestamps, and split ratios.

Instructions

Yahoo Finance corporate actions. Returns the corporate actions for a Yahoo Finance symbol such as AAPL: dividends, splits and capital_gains. Dividend and capital-gain entries carry a Unix timestamp and an amount; split entries carry a ratio such as 4:1.

Input Schema

NameRequiredDescriptionDefault
symbolYesYahoo Finance symbol such as AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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. It does disclose the shape of returned entries (Unix timestamps and amounts for dividends/capital gains, ratios like '4:1' for splits), which is real behavioral value, but it says nothing about rate limits, auth, or that this is a read-only operation.

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 the resource and input front-loaded, followed by return-shape detail. Nothing is padded, though the opening 'Yahoo Finance corporate actions' fragment is mild redundancy.

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 and no annotations, the description compensates by describing the returned entry types and their fields, which is exactly what an agent needs for a single-parameter read tool. Auth and rate-limit behavior remain unaddressed but are minor here.

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% and there is a single required parameter, so the baseline is 3. The description repeats the symbol concept and example (AAPL) already present in the schema, adding no syntax or format guidance beyond it.

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) and resource (corporate actions) for a named input (symbol), and enumerates the exact event types returned (dividends, splits, capital_gains). It does not explicitly distinguish itself from siblings like yahoo_finance_ticker_dividends or yahoo_finance_ticker_splits, but the aggregating nature is clear.

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: fetch all corporate actions for a symbol in one call rather than hitting the per-type siblings. No explicit when-to-use statement or mention of alternatives, so the agent must infer the routing decision.

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