Fetch dividend events for a Yahoo Finance ticker symbol to review payout history, ex-dates, and amounts. Enter a symbol like AAPL to get structured dividend data.
Yahoo Finance dividends. Returns dividend events for a symbol.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Yahoo Finance symbol such as AAPL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full burden for behavioral traits. It does not mention what dividend events include (e.g., dates, amounts, types), whether the data is historical or current, or any limitations. The word 'events' is vague.
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?
Two short sentences with no redundancy. Every word adds value: the tool name, the data source, and the action. Highly 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?
Lacks details about the structure of the response (e.g., date, amount, type). Without an output schema, the description should clarify what dividend events are returned, but it doesn't. Incomplete for a financial data tool.
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% with a single parameter 'symbol' described as 'Yahoo Finance symbol such as AAPL'. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.
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 the tool returns dividend events for a given symbol. The verb 'returns' and resource 'dividend events' are specific, and the tool is easily distinguished from siblings like yahoo_finance_ticker_splits or yahoo_finance_ticker_info.
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 other Yahoo Finance tools that might also provide dividend data (e.g., yahoo_finance_ticker_financials). No prerequisites or context for when dividend events are available.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.