Yahoo Finance MCP Server

Option chain

get_options

Read-only

Fetch a Yahoo symbol's option chain: omit expiration to list available dates, or pass a YYYY-MM-DD date to get calls and puts for that expiration.

Instructions

Get the option chain for a Yahoo symbol.

Call without expiration to list available expiration dates. Call with an expiration (YYYY-MM-DD from that list) to get the calls and puts for that date, up to 60 strikes each centred on the current price, with truncated set when a wider chain was cut. Yahoo carries chains for US-listed instruments only, so a non-US symbol has none and that says nothing about the symbol.

Input 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.
`expiration`	No	Expiration date 'YYYY-MM-DD' from the list returned when called without it. Omit to list available expiration dates.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.8.6Oct 17, 2026
- removedInput schema / properties / expiration / title
```
Removed value: -"Expiration"
```
- removedInput schema / properties / symbol / title
```
Removed value: -"Symbol"
```
- removedInput schema / title
```
Removed value: -"get_optionsArguments"
```
- removedOutput schema / title
```
Removed value: -"get_optionsDictOutput"
```
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.9/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses real behavioral traits: a 60-strike cap centred on current price, a `truncated` flag when a wider chain is cut, and the US-listing-only coverage rule with an explicit warning against misreading an empty result. This is exactly the context annotations cannot carry.

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?

Front-loaded with the core purpose, then two tight sentences covering the two invocation modes and the coverage caveat. No filler; every sentence carries information an agent needs to call correctly.

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?

An output schema exists, so return structure need not be spelled out, yet the description still flags the `truncated` field an agent should check. Combined with the mode switching and the non-US caveat, nothing needed to invoke or interpret this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: `expiration` must be a value drawn from the list returned by the parameterless call, and it changes the response shape from an expiration list to calls/puts. The two-mode semantics are explained rather than restated.

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 the option chain') for a named source (Yahoo symbol), which is clearly distinct from siblings like get_quote, get_history or get_financials. An agent can identify this as the derivatives-data tool without opening the schema.

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

Usage Guidelines5/5

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

The description explicitly branches usage: call without `expiration` to enumerate available expiration dates, call with one to retrieve calls/puts for that date. It also flags the case where a non-US symbol yields nothing and warns that this says nothing about the symbol itself, preventing a wrong inference.

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