Skip to main content
Glama

TejHQ Indian Markets

Futures history

fo_futures
Read-onlyIdempotent

Daily futures rows of one underlying, every expiry, over a date range. 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_futures"
  }
}

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.
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.1/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 250-row ceiling and ordering, the 90-day fallback window, the dataset start date and exchange scope, the exclusion of intraday data, and the access tier requirement with a link. These are exactly the operational constraints an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, and every following sentence carries distinct information: defaults, row cap and ordering, dataset boundaries, access tier. The telegraphic style is dense rather than padded.

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 still conveys the shape of a result (daily rows per expiry, ordered by date then expiry) and all gating conditions. It omits what fields a row contains (e.g., OHLC, OI, settlement) and whether prices are adjusted, which would fully close the gap for a timeseries tool.

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 the schema already explains symbol, from, to, limit, and offset including the meta.next_offset paging hint. The description reinforces the symbol requirement and the default window but adds no new parameter meaning, so the baseline of 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?

The first sentence gives a specific verb+resource+scope: daily futures rows for one underlying, all expiries, over a date range. That is enough for an agent to distinguish it from chain/contract-style siblings like fo_chain or fo_contract, though no sibling is named explicitly.

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 states the required parameter, the implicit default window when from/to are omitted, the row cap, and the data boundaries (NSE equity derivatives only, from 2010-01-04, no BSE, no intraday). It does not name an alternative tool or say when not to use this one, so it stops short of full routing guidance.

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