Skip to main content
Glama
Unofficial Yahoo Finance MCP Server

Unofficial Yahoo Finance MCP Server

Quote

get_quote
Read-only

Fetch current price and key intraday figures for one Yahoo Finance symbol, including previous close, open, day range, volume, market cap, and moving averages.

Instructions

Get the current price and key intraday figures for a Yahoo symbol.

One symbol: currency, exchange, last price, previous close, open, day high/low, volume, market cap, 50- and 200-day averages and the 52-week range and change. To compare several symbols use get_quotes, for past prices get_history, for valuation and the business profile get_company_info. No timestamp comes with the price, and Yahoo may show it with the exchange's delay. 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": {
      "symbol": "<symbol>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesA Yahoo ticker or an ISIN, e.g. 'AAPL', 'SAP.DE' or 'US0378331005'. For a company name, use 'search' first.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safe-read, open-world profile, and the description adds real behavioral caveats beyond them: no timestamp accompanies the price, Yahoo may report it with the exchange delay, and a cryptocurrency's market cap is null here with a pointer to where it is available. It stops short of error behavior or rate limits, so it is strong but not exhaustive.

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 the core action, then the field list, then alternates, then data-quality caveats – a sensible order with no filler sentences. The field enumeration is dense but each item helps an agent decide whether this tool returns what it needs.

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

Completeness4/5

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

For a one-parameter read tool with annotations and an output schema, the definition covers purpose, alternatives, and known data-quality edge cases (delay, missing timestamp, null crypto market cap). The returned-field list is somewhat redundant with the output schema, but it does no harm and aids selection.

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% and the single `symbol` parameter is already documented with ticker/ISIN examples and the 'use search for a company name' hint. The description still adds the cardinality rule ('One symbol'), which is a meaningful constraint given the sibling `get_quotes` takes many.

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?

Specific verb ('Get') plus a single, well-scoped resource (current price and key intraday figures for one Yahoo symbol), and it enumerates the exact fields returned so the agent knows what it gets. It explicitly separates itself from `get_quotes` (multiple symbols), `get_history` (past prices) and `get_company_info` (valuation/profile).

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?

It names each alternative and the condition that selects it: several symbols to `get_quotes`, past prices to `get_history`, valuation/business profile to `get_company_info` (also for crypto market cap). The singular-symbol constraint is stated up front, so nothing about when to pick this tool is left to inference.

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