Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance option chain

yahoo_finance_options_get
Read-onlyIdempotent

Retrieve Yahoo Finance option expiries, strikes, calls, and puts for a ticker symbol to compare contracts and support options analysis.

Instructions

Get Yahoo Finance option expiries, strikes, calls and puts. 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_options_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
straddleNoPair calls and puts by strike. Default: false.
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.
expirationNoExpiry date in ISO 8601 form, for example `2026-12-18`. Must be one of the dates returned in `expirations`; omit it for the nearest expiry.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered without prose. The description adds an implicit statement of what is returned (expiries, strikes, calls, puts), useful given there is no output schema, but it silently omits the multi-call handshake implied by `conversation_id` (echo the server's id, no parallel calls) and that `expiration` must match a returned expiry.

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 sentences with no filler, and the resource enumeration is front-loaded before the prerequisite. It is efficiently sized, though the terseness leaves no room for the behavioral notes an open-world, six-parameter tool arguably needs.

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

Completeness3/5

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

For a tool with six parameters, three required, a non-standard context/llm_model/conversation_id contract, an open-world hint and no output schema, the description is thin. The field list partially compensates for the absent output schema, but the sequencing constraint on `conversation_id` and the expiry-selection rule matter for correct invocation and are absent from the prose.

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%, so all six parameters, including the unusual `context`, `llm_model` and `conversation_id` fields, are already documented in the schema. The description only reiterates `symbol` requires, adding no syntax, defaults, or interaction detail beyond the structured fields, so the baseline 3 applies.

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?

A concrete verb ('Get') plus a specific resource ('Yahoo Finance option expiries, strikes, calls and puts'), which cleanly separates it from every listed sibling that covers chart, quote, profile, or fundamentals data. It stops short of explicitly naming an alternative to use instead, relying on the resource noun alone to distinguish it.

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

Usage Guidelines3/5

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

The only guidance is a restatement of the required parameter ('Requires `symbol`'), which the schema already enforces via required: true. Nothing tells the agent when an option chain is the right retrieval versus chart or instrument lookups, or when to set `straddle` or pin a specific `expiration`.

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