Yahoo Finance MCP Server

Quotes for several symbols

get_quotes

Read-only

Fetch current prices and key stats for multiple Yahoo tickers in one call for comparison. Returns currency, last price, previous close, open, day high/low, and market cap per symbol.

Instructions

Get compact current quotes for several Yahoo symbols in one call.

Use this to compare or fetch prices for multiple tickers at once. Each symbol is looked up individually and returns currency, last price, previous close, open, day high/low, and market cap. Symbols that return no data are listed under not_found rather than failing the whole call, and truncated is set when more than 50 were passed.

Input Schema

Name	Required	Description	Default
`symbols`	Yes	Yahoo tickers or ISINs, e.g. ['AAPL', 'MSFT', 'SAP.DE']. Not company names. Up to 50, extras are dropped.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.8.6Oct 17, 2026
- removedInput schema / properties / symbols / title
```
Removed value: -"Symbols"
```
- removedInput schema / title
```
Removed value: -"get_quotesArguments"
```
- removedOutput schema / title
```
Removed value: -"get_quotesDictOutput"
```
Changed1 schema field changedv0.7.0Oct 1, 2026
- addedInput schema / properties / symbols / items / maxLength
```
Added value: +32
```

Changed1 schema field changedv0.4.0Aug 18, 2026

changedInput schema / properties / symbols / description

Previous value: -"A list of native Yahoo Finance ticker symbols, e.g. ['AAPL', 'MSFT', 'SAP.DE']. Each must be a native ticker, never an ISIN, WKN, or company name; resolve those via 'search' first. Up to 50 symbols; extras are dropped (the result flags this as truncated)."New value: +"Yahoo tickers or ISINs, e.g. ['AAPL', 'MSFT', 'SAP.DE']. Not company names. Up to 50, extras are dropped."

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 read-only/open-world safety profile, and the description adds genuinely new behavior: per-symbol independent lookup, partial failure routed to `not_found` instead of aborting, and `truncated` being set past 50 symbols. The field list adds little because an output schema already exists, but the failure and truncation semantics are real added value.

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 tight sentences, front-loaded with the core capability, then usage, then return/failure semantics. No filler and no repetition of the schema.

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 one-parameter batch quote tool with an output schema, the description covers everything the agent needs: what is fetched, the cap, partial-failure handling, and the truncation flag. Return value details are correctly left to the output schema.

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 description coverage is 100% for the single `symbols` parameter, so the schema already documents tickers/ISINs, the 50-item cap, and the no-company-names rule. The description restates the cap and ties it to the `truncated` output flag, which is a marginal addition rather than new parameter meaning.

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 quotes) plus a clear scope qualifier ("several Yahoo symbols in one call"), which implicitly but unambiguously separates it from the singular get_quote sibling. An agent can pick the batch tool without opening either schema.

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?

"Use this to compare or fetch prices for multiple tickers at once" gives a concrete when-to-use condition. It never names the single-symbol alternative (get_quote) or states an exclusion, so it stops just short of full routing guidance.

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