Skip to main content
Glama
Sign In

FinzData market data

by io.github.FinzData
OverviewDiscussionsAdmin

Get index bars (SPX, NDX, VIX, ...)

get_index
Read-onlyIdempotent

Answers 'what did the S&P 500 (or VIX) do?' Give a symbol (index, e.g. SPX, NDX, VIX, RUT, DXY) and optionally interval (1min, 5min, 15min, 30min, 1hour or 1day, default 1day) plus start and end. Returns OHLC bars, times in US Eastern, clipped to as_of. Covers 123 indexes: S&P 500, Nasdaq-100, Dow, Russell 2000, VIX and its term structure, sector and style indexes, DAX, AEX, the dollar index and Treasury yield indexes. Free keys get daily bars for the last 12 months; paid keys get every bar size.

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

Input Schema

NameRequiredDescriptionDefault
endNo
as_ofNoPoint-in-time cutoff (YYYY-MM-DD). Nothing dated after this is returned, preventing look-ahead bias. Defaults to today (UTC).
startNo
symbolYesIndex symbol, e.g. SPX, NDX, VIX, RUT, DXY.
intervalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the marginal bar is met by the description disclosing return shape (OHLC bars), timezone (US Eastern), the as_of clipping that prevents look-ahead, and tier-based history limits (12 months daily free vs all bar sizes paid). Gaps are minor: no mention of invalid-symbol behavior or maximum range per request.

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 question it answers, then inputs, then outputs, then coverage and tier limits — a sensible ordering with no filler. The 123-index enumeration is long but does real work by letting an agent validate symbol choice, so it earns most of its length.

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 correctly carries the return-value burden (OHLC bars, Eastern timestamps, as_of clipping) and adds coverage scope. Only edge-case behavior such as unknown symbols or per-request bar limits is missing, which is modest for a five-parameter read tool.

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 only 40%, but the description compensates by enumerating symbol examples, spelling out the full interval enum with its default, and referencing start/end and the as_of cutoff. Only the string format of start/end (date vs datetime) is left unstated in both places.

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?

Opens with a concrete user question it answers and names the exact resource class (index bars) with example symbols SPX, NDX, VIX, RUT, DXY. Against siblings like get_bars, get_fx, get_futures, get_crypto and get_crypto, the index scope makes selection unambiguous without opening the schema.

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?

Explains what to supply (symbol, optional interval, start/end) and the default interval of 1day. It also states the free-key vs paid-key access conditions, which is real usage guidance. It does not explicitly say when to prefer this over get_bars or get_futures for index-like exposures, so it stops short of naming alternatives.

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