Skip to main content
Glama
Unofficial Yahoo Finance MCP Server

Unofficial Yahoo Finance MCP Server

Quotes for several symbols

get_quotes
Read-only

Fetch current quotes for multiple Yahoo Finance tickers in one call to compare prices, currency, previous close, open, day high/low, and market cap; missing symbols are reported separately.

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. A cryptocurrency's market cap is null here, get_company_info has it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbols": "<symbols>"
    },
    "name": "get_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesYahoo tickers or ISINs, e.g. ['AAPL', 'MSFT', 'SAP.DE']. Not company names. Up to 50, extras are dropped.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.8.6
    • removedInput schema / properties / symbols / title
      Removed value: -"Symbols"
    • removedInput schema / title
      Removed value: -"get_quotesArguments"
    • removedOutput schema / title
      Removed value: -"get_quotesDictOutput"
  2. Changed1 schema field changedv0.7.0
    • addedInput schema / properties / symbols / items / maxLength
      Added value: +32
  3. Changed1 schema field changedv0.4.0
    • 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."
  4. First observedv0.2.2

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the failure model (per-symbol lookup, misses collected under `not_found` instead of failing the call), the truncation behavior past 50 symbols, and a data quirk (null crypto market cap, available via get_company_info). These are exactly the traits an agent needs to interpret partial results correctly.

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

Conciseness4/5

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

Front-loaded with purpose, then usage, then return/failure semantics — a sensible order with no filler sentences. There is mild redundancy in enumerating return fields when an output schema exists, but the text stays tight overall.

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 read with an output schema and read-only annotations, the description covers everything an agent still needs: batch rationale, partial-failure handling, truncation limits, and a known edge case for crypto. Nothing material about invoking or interpreting the call is left implicit.

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 single `symbols` parameter is already fully described (tickers/ISINs, not names, up to 50). The description adds only the per-symbol lookup model and restates the 50-symbol cap via `truncated`, so the schema does the heavy lifting and baseline 3 applies.

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?

"Get compact current quotes for several Yahoo symbols in one call" states a specific verb (get), resource (quotes), and scope (batch of symbols), which cleanly separates it from the singular get_quote sibling. The follow-up sentence reinforces the batch use case ("multiple tickers at once"), so an agent can pick it 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 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 clear selecting context and implicitly excludes single-symbol lookups. It stops short of naming get_quote as the alternative or stating when not to use it, so it falls 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.