Yahoo Finance MCP Server

get_calendar

Read-only

Fetch upcoming earnings and dividend dates for a Yahoo equity symbol, including analyst estimate ranges and ex-dividend schedules.

Instructions

Get upcoming corporate-calendar events for a Yahoo symbol.

Returns the next earnings date(s) with analyst estimate ranges and the next dividend / ex-dividend dates. Equity-only: an ETF, fund or crypto symbol answers with an error that says so.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	Yes	A Yahoo ticker or an ISIN, e.g. 'AAPL', 'SAP.DE' or 'US0378331005'. For a company name, use 'search' first.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Oct 1, 2026
- addedInput schema / properties / symbol / maxLength
```
Added value: +32
```

Changed1 schema field changedv0.4.0Aug 18, 2026

changedInput schema / properties / symbol / description

Previous value: -"A native Yahoo Finance ticker symbol, e.g. 'AAPL', 'MSFT', 'SAP.DE', or 'BMW.DE'. This is NOT an ISIN, a WKN, or a company name, and must NOT be built by appending an exchange suffix to an ISIN (e.g. 'US0378331005.DE' is invalid). If you only have a name or ISIN, call the 'search' tool first and pass the 'symbol' value it returns."New value: +"A Yahoo ticker or an ISIN, e.g. 'AAPL', 'SAP.DE' or 'US0378331005'. For a company name, use 'search' first."

First observedv0.2.2Aug 2, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover the safety profile (readOnlyHint, openWorldHint), so the description's added value is the error behavior for non-equity symbols and the shape of the returned data. It does not mention rate limits or symbol-normalization quirks, but for a read-only lookup it is adequately transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and return contents, with the equity-only caveat placed last. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with an output schema and covering annotations, the description supplies everything an agent needs: what is returned, the equity scope, and the failure mode. Nothing essential 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% and the schema already explains the symbol format (ticker or ISIN) plus the advice to use 'search' for company names. The description adds only the equity-only constraint on the symbol, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get upcoming corporate-calendar events) and enumerates exactly what comes back: next earnings date(s) with estimate ranges plus dividend/ex-dividend dates. This clearly separates it from narrower siblings like get_earnings and get_dividends.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit when-not: non-equity symbols (ETF, fund, crypto) return an error. It does not, however, route the agent to specific alternatives such as get_dividends or get_earnings when only one piece of the calendar is wanted, so alternative-selection guidance is partial.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.