Skip to main content
Glama

TejHQ Indian Markets

Option chain

fo_chain
Read-onlyIdempotent

End of day option chain of one underlying for one expiry on one date: settle price, open interest, contracts and more for each strike and option type, plus iv, delta, gamma, theta and vega on contracts that traded that day (Black-76 on the same-expiry forward; iv 0.14 means 14%). On an expiry date the nearest expiry is the one expiring that day, which has no Greeks: pass the next expiry from fo_expiries. Required: symbol. date defaults to the latest day with data; expiry defaults to the nearest expiry. A full chain can run to hundreds of rows, so this returns the 40 rows with strikes nearest the underlying by default, up to 200, sorted by strike (meta.centered_on). Use strike_min, strike_max and option_type to pick another part of the chain. End of day NSE equity derivatives from 2010-01-04, no BSE, no intraday. Tier: needs a Retail or Pro key (https://tejhq.dev/upgrade).

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

Input Schema

NameRequiredDescriptionDefault
dateNoTrading date. Default: latest. Format YYYY-MM-DD.
limitNoMost rows to return.
expiryNoExpiry date. Default: nearest. See fo_expiries. Format YYYY-MM-DD.
symbolYesUnderlying symbol, for example NIFTY, BANKNIFTY, RELIANCE. Case does not matter.
strike_maxNoHighest strike to include.
strike_minNoLowest strike to include.
option_typeNoOnly this option type: CE or PE, or CA or PA before 2011.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the Greeks methodology (Black-76 on the same-expiry forward), the iv unit convention (0.14 = 14%), and the non-obvious trap that the expiry-dated contract carries no Greeks. It also explains the row-selection behavior (40 strikes nearest the underlying, up to 200, sorted by strike, meta.centered_on) and the Retail/Pro key requirement, which the annotations do not convey.

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?

Purpose is front-loaded in the first clause, and nearly every sentence carries operational information (Greeks caveat, defaults, row window, coverage limits). It is a single dense block with parentheticals, so it is longer than ideal for scanning, but I found no filler to cut.

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

Completeness5/5

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

For a 7-parameter read-only tool with no output schema, the definition covers return fields, Greek semantics, defaults, pagination behavior, authorization tier, and data coverage boundaries. An agent has everything needed to call it correctly and interpret the result without guessing.

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 100%, so the baseline is 3, but the description adds real meaning the schema lacks: date defaults to the latest day with data, expiry defaults to the nearest, expiry selection interacts with Greek availability, and limit is the window centered on the underlying rather than an arbitrary head. That explains why strike_min/strike_max exist alongside limit.

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?

"End of day option chain of one underlying for one expiry on one date" states a specific verb-like resource with all three scoping dimensions, then enumerates the returned fields (settle price, open interest, contracts, iv/delta/gamma/theta/vega per strike and option type). It also bounds the domain (NSE equity derivatives from 2010-01-04, no BSE, no intraday), so an agent can immediately distinguish this from fo_contract or fo_futures.

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?

It gives explicit context for use and a concrete alternative: on an expiry date, pass the next expiry obtained from fo_expiries. It also tells the agent how to reach other slices of the chain via strike_min/strike_max/option_type when the default 40-row window is not what is wanted. The only gap is that it never explicitly contrasts with fo_contract for a single-strike lookup, but the surrounding guidance is enough to route correctly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources