Return capital gains data for ETF or mutual fund symbols supported by Yahoo Finance. Provide clean JSON for tax reporting and investment analysis.
Yahoo Finance capital gains. Returns capital gain events for ETF or mutual fund symbols when Yahoo provides them.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Yahoo Finance symbol such as SPY |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that data availability depends on Yahoo providing it, and restricts to ETF/mutual fund symbols. However, it does not mention other behavioral traits such as rate limits, read-only nature, or what happens if no data is found.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long and directly conveys the purpose without any extraneous information. It is appropriately front-loaded and concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with one parameter, and the description covers the core purpose. However, without an output schema, it would benefit from mentioning the structure of the returned data (e.g., a list of events with dates and amounts).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter 'symbol', with a schema description already specifying 'Yahoo Finance symbol such as SPY'. The description adds no additional semantic guidance beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool returns capital gain events for ETF or mutual fund symbols. It specifies the resource (capital gains) and the verb (returns), and implicitly distinguishes from other yahoo_finance_ticker_* tools, though it could be more explicit about what constitutes a capital gain event.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like yahoo_finance_ticker_dividends or yahoo_finance_ticker_earnings. No when-not-to-use or prerequisite information is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.