Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_capital_gains

Fetch capital gain events for a Yahoo Finance symbol, mainly ETFs and mutual funds, with Unix timestamps and amounts, plus dividends and splits.

Instructions

Yahoo Finance capital gains. Returns capital gain events for a Yahoo Finance symbol, mainly ETFs and mutual funds such as SPY, each with a Unix timestamp and an amount, when Yahoo provides them. The response object also has dividends and splits fields.

Input Schema

NameRequiredDescriptionDefault
symbolYesYahoo Finance symbol such as SPY

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?

With no annotations, the description carries the full burden. It usefully discloses the return shape (Unix timestamp + amount, plus dividends and splits fields) and caveats that data appears 'when Yahoo provides them', but says nothing about auth, rate limits, or that it is a read-only lookup.

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 sentences, front-loaded with the tool's purpose. The opening 'Yahoo Finance capital gains.' is slightly redundant with the following sentence but overall it is tight and readable.

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?

For a one-parameter fetch tool with no output schema, the description does a fair job of previewing the return fields and their format. It could say more about field semantics or empty-response behavior, but nothing essential for invoking the tool is missing.

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% for the single 'symbol' parameter, so the schema already documents it. The description restates the symbol and adds example values (SPY), which is marginal value rather than new semantics. 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 clear verb+resource: it returns capital gain events for a Yahoo Finance symbol, with examples (SPY) and the asset classes where it applies. It does not explicitly distinguish itself from the sibling tools yahoo_finance_ticker_dividends or yahoo_finance_ticker_splits, even though it mentions those as response fields.

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?

Implied usage comes from 'mainly ETFs and mutual funds such as SPY', which tells the agent when this tool is relevant. However there is no explicit when-to-use vs. sibling tools (dividends, splits, actions), and no prerequisites or conditions beyond the asset-class hint.

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