Skip to main content
Glama
Sign In

FinzData market data

by io.github.FinzData
OverviewDiscussionsAdmin

Get end-of-day options chains

get_options_eod
Read-onlyIdempotent

End-of-day US options chains since January 2010 for 5,800+ underlyings (stocks, ETFs and indexes, delisted included): every strike and expiry each day with last, bid, ask, bid and ask implied volatility, open interest, volume, delta, gamma, vega, theta and rho. Give symbol and day (YYYY-MM-DD; default the latest day); optional expiry (YYYY-MM-DD) and right (C or P) narrow the chain. Clipped to as_of. Free keys get the last 12 months; FinzData Options EOD gives the full history: one underlying $49, Magnificent 7 + SPY + QQQ $495, every underlying $2,950 (https://finzdata.com/options-eod-data).

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_options_eod"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoTrading day YYYY-MM-DD; default the latest day.
as_ofNoPoint-in-time cutoff (YYYY-MM-DD). Nothing dated after this is returned, preventing look-ahead bias. Defaults to today (UTC).
rightNo
expiryNoOptional expiry YYYY-MM-DD.
symbolYesUnderlying, e.g. AAPL, SPY, SPX.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses that results are clipped to as_of (preventing look-ahead), that free keys are limited to the trailing 12 months, and that full history requires paid tiers. It does not say anything about row/size limits or pagination for a full chain, which is the main remaining unknown.

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?

The purpose and field list are front-loaded, and the second sentence cleanly explains the filters. The closing pricing sentence is long and somewhat promotional, but it carries real entitlement information an agent needs to explain truncated results.

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?

With no output schema, the description compensates by enumerating the returned columns, so an agent knows the shape of the response. The only omissions are response volume/pagination behavior and whether a full chain is truncated, which matter for a tool returning every strike and expiry.

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 80%, so most parameters are already documented in the schema. The description adds meaning mainly for the undocumented `right` (C or P narrows the chain) and reiterates day/expiry defaults, but adds nothing about as_of or symbol beyond what the schema states. Baseline 3 plus minor value.

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+resource ('End-of-day US options chains'), the coverage (since January 2010, 5,800+ underlyings, stocks/ETFs/indexes, delisted included), and the exact fields returned (strike, expiry, last, bid, ask, IV, OI, volume, greeks). No sibling tool returns options chains, and an agent can tell instantly what this does.

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 clear calling guidance: symbol and day are the primary selectors (day defaults to latest), while expiry and right are described as narrowing filters. It does not name an alternative tool or state when not to use this one, but no sibling provides an obvious substitute, so the practical gap is small.

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

All FinzData market data toolsInspect
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