Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance chart

yahoo_finance_chart_get
Read-onlyIdempotent

Fetch Yahoo Finance chart bars, dividends, splits, and capital gains for a ticker symbol to analyze price history and corporate events.

Instructions

Get Yahoo Finance chart bars, dividends, splits and capital gains. Requires symbol.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yahoo_finance_chart_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoWindow end, as an ISO 8601 date or time or epoch seconds. It is exclusive: bars before it are returned. It takes precedence over `range`.
rangeNoA named window such as `1y`, `5y` or `max`. Ignored when `start` or `end` is sent; those define the window. Default: `1y` when neither is sent.
startNoWindow start, as an ISO 8601 date or time (such as `2026-01-31`) or epoch seconds. A time with no zone is UTC. It takes precedence over `range`.
eventsNoCorporate events to include: `div`, `split`, `capitalGain`, comma-separated. Default: `div,split`.
symbolYesRequired. Ticker symbol, case-insensitive, e.g. `AAPL`, `^GSPC`, `EURUSD=X`, `BTC-USD`, `7203.T`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
intervalNoBar size. Default: `1d`. `1m` bars cover the last 30 days, at most 8 days per request. `2m`, `5m`, `15m`, `30m` and `90m` cover at most 60 days; `60m`, `1h` and `4h` at most 730 days.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.
includeExtendedHoursNoInclude pre-market and post-market bars. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the description needed to add only context beyond that. Instead it adds nothing: no mention of pagination, rate limits, response shape, or that this returns time-series data rather than a point-in-time quote. 'Requires `symbol`' duplicates the schema.

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?

Two short, front-loaded sentences with the resource and payload up front. The second sentence is pure redundancy with the schema's required field, so it does not fully earn its place.

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

Completeness2/5

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

For a 10-parameter tool with no output schema, the description should at least sketch what a chart response contains and note the conversation_id echo protocol implied by the schema. It provides neither, leaving the agent to infer return structure entirely.

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%, including interval/range precedence rules and event defaults, so the schema carries parameter meaning fully. The description adds no syntax or interpretation beyond repeating the required symbol, which merits the baseline 3 under high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('Yahoo Finance chart') and enumerates the payload: bars, dividends, splits and capital gains. That is enough to separate it from siblings like quotes_list or financials_list, though the description never names or contrasts an alternative.

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

Usage Guidelines2/5

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

The only usage statement is 'Requires `symbol`', which restates a required field already in the schema. Nothing tells the agent when to prefer a chart over quotes_list or instrument_get, nor any prerequisite or exclusion.

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

Deploy Server

Other Tools