Fetch Yahoo Finance calendar events for a stock symbol, such as earnings or dividend dates, to track upcoming company milestones.
Yahoo Finance calendar. Returns Yahoo Finance calendar 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?
No annotations are provided, so the description must fully disclose behavior. It only states that it returns calendar events, without any details on data freshness, pagination, rate limits, or authentication requirements. The minimal description does not adequately inform the agent of potential side effects or constraints.
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 concise at two sentences, with the key verb and resource front-loaded. However, it sacrifices clarity for brevity, missing an opportunity to specify the event type.
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?
Despite the tool's simplicity (single parameter, no output schema), the description is incomplete. It does not clarify what 'calendar events' encompass, leaving ambiguity. Given the richness of sibling tools, more detail is needed for proper context.
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?
The input schema has 100% coverage (symbol parameter is described as 'Yahoo Finance symbol such as AAPL'). The tool description adds no additional meaning beyond the schema, matching the baseline score of 3 for full schema coverage.
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 states the verb 'returns' and the resource 'Yahoo Finance calendar events for a symbol', but it does not specify what kind of calendar events (e.g., earnings, dividends, splits). This vagueness makes it hard to distinguish from sibling tools like yahoo_finance_ticker_earnings or yahoo_finance_calendar_results.
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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, scenarios, or exclusions, leaving the agent without context to choose appropriately among many similar finance calendar tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.