SiteCheck Crypto & Finance

Yahoo Finance quote and daily history for one ticker

finance_yahoo_finance

Read-only

Yahoo Finance quote and daily history for one ticker (stocks, ETFs, indices, FX, crypto symbols) from Yahoo's public chart endpoint. Prices are delayed or end-of-day per Yahoo; no fundamentals or company lists are included. Related tools on this server, for a different need: finance_finviz when you need Finviz quote snapshot for one stock ticker: the key; finance_stockanalysis when you need StockAnalysis company identity for one stock ticker. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "finance_yahoo_finance"
  }
}

Input Schema

Name	Required	Description	Default
`range`	No	History range: 1d, 5d, 1mo, 3mo, 6mo, 1y, 2y, 5y, 10y, ytd, max (default 5d)
`symbol`	Yes	Yahoo ticker, e.g. AAPL, MSFT, ^GSPC, EURUSD=X, BTC-USD

Output Schema

Name	Required	Description	Default
`name`	No
`price`	No
`range`	No
`change`	No
`dayLow`	No
`source`	No
`symbol`	No
`volume`	No
`dayHigh`	No
`history`	No
`currency`	No
`exchange`	No
`checkedAt`	No
`marketTime`	No
`changePercent`	No
`previousClose`	No
`fiftyTwoWeekLow`	No
`fiftyTwoWeekHigh`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing data latency ("Prices are delayed or end-of-day per Yahoo"), scope limits (no fundamentals or company lists), and concrete billing terms: $0.002 USDC per successful call via x402 on Base/Solana/Arc, with failed calls not charged. Cost and latency disclosure is exactly the context an agent cannot infer from structured fields.

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

Conciseness3/5

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

The purpose and pricing are front-loaded and useful, but the sibling-tool sentence is garbled ("finance_finviz when you need Finviz quote snapshot for one stock ticker: the key;") and reads like templated filler. A cleaner two-clause routing statement would have carried the same information with less noise.

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?

An output schema exists, so return values need not be described; cost, latency, symbol formats and exclusions are all covered. The only residual ambiguity is whether sub-daily ranges return intraday bars given the "daily history" phrasing, which matters for a 2-param tool with an interval-less 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 coverage is 100% and both parameters (symbol examples like ^GSPC, EURUSD=X, BTC-USD; range enum values) are already fully documented in the schema. The description adds only the asset-class framing and does not clarify granularity — "daily history" sits slightly at odds with ranges like 1d/5d, but the schema's enum resolves it. 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?

States a specific verb and resource — a quote plus daily history for one ticker — and enumerates the covered asset classes (stocks, ETFs, indices, FX, crypto) plus the source endpoint. It also names the two sibling tools it is not (finance_finviz, finance_stockanalysis), so an agent can differentiate without opening schemas.

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?

Gives explicit routing conditions for the related tools: use finance_finviz for a Finviz quote snapshot and finance_stockanalysis for company identity. It also states what is out of scope ("no fundamentals or company lists"). It does not address the many other price/history siblings such as finance_stooq_historical_stocks or finance_alpha_vantage_public, so the routing is clear but not exhaustive.

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

All SiteCheck Crypto & Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?