Skip to main content
Glama

TejHQ Indian Markets

F&O daily stats and IV history

fo_stats
Read-onlyIdempotent

Daily figures per expiry for one underlying, computed by TejHQ: put-call ratio by open interest and by volume, max pain, futures settle change and buildup (long_buildup, short_buildup, short_covering, long_unwinding), basis, rollover_pct, atm_iv (implied volatility at the strike nearest the forward, 0.14 means 14%) and iv_skew (25-delta put IV minus 25-delta call IV). is_nearest marks the nearest expiry each day. A long from and to gives an IV or PCR history back to 2010. Required: symbol. Without from and to it returns the last 90 days. Up to 250 rows per call, by date then expiry. 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_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, inclusive. Default: today. Format YYYY-MM-DD.
fromNoFirst date, inclusive. Default: 90 days before to. Format YYYY-MM-DD.
limitNoMost rows to return.
expiryNoOnly this expiry. Format YYYY-MM-DD.
offsetNoRows to skip, for paging. Use meta.next_offset from a truncated result.
symbolYesUnderlying symbol, for example NIFTY, BANKNIFTY, RELIANCE. Case does not matter.

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?

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: data provenance and coverage limits (EOD only, NSE only, no BSE, back to 2010-01-04), row cap and ordering ('by date then expiry'), and an explicit auth/tier requirement with an upgrade link. It also defines ambiguous values inline (atm_iv 0.14 means 14%, iv_skew as 25-delta put IV minus 25-delta call IV) and explains is_nearest.

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 resource and metric list, then usage defaults, then coverage and tier constraints. Dense but nearly every clause carries information an agent needs; the buildup parenthetical and metric definitions add length, though they resolve genuine ambiguity rather than padding.

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?

Six parameters and no output schema, so the description carries the return-value burden and does it well by naming each field and its meaning, plus row caps, ordering, and pagination behavior. Coverage limits and the tier/key requirement round out what an agent needs before calling.

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 baseline is 3, but the description adds real meaning: the from/to defaults and the notion of a 'history' query, the 250-row ceiling interacting with limit/offset, and the row ordering that makes paging predictable. It does not explain the expiry param or the from/to vs expiry interaction, which the schema also leaves implicit.

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 resource and scope: 'Daily figures per expiry for one underlying', then enumerates the concrete metrics returned (PCR by OI and volume, max pain, futures settle change, buildup taxonomy, basis, rollover_pct, atm_iv, iv_skew). This is clearly distinguishable from chain/contract siblings at fo_chain or fo_contract, since it delivers aggregated per-expiry daily stats plus IV history rather than a live chain.

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 actionable context: symbol is required, omitting from/to yields the last 90 days, and a long from/to produces an IV or PCR history back to 2010. It also bounds usage with 'Up to 250 rows per call' and 'End of day NSE equity derivatives from 2010-01-04, no BSE, no intraday'. No explicit routing to alternatives (fo_chain, unusual_history, fo_expiries), so it stops short of a 5.

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