Skip to main content
Glama

TejHQ Indian Markets

One F&O contract

fo_contract
Read-onlyIdempotent

Daily history of one contract. With expiry alone it is the future for that expiry; with strike and option_type together it is that option, with iv and Greeks on days it traded. Required: symbol, expiry. to defaults to expiry, from to 6 months before to. Up to 250 rows per call, oldest first. 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>",
      "expiry": "<expiry>"
    },
    "name": "fo_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, inclusive. Default: the expiry. Format YYYY-MM-DD.
fromNoFirst date, inclusive. Default: 6 months before to. Format YYYY-MM-DD.
limitNoMost rows to return.
expiryYesExpiry date of the contract. Format YYYY-MM-DD.
offsetNoRows to skip, for paging. Use meta.next_offset from a truncated result.
strikeNoStrike price. Pass with option_type.
symbolYesUnderlying symbol, for example NIFTY, BANKNIFTY, RELIANCE. Case does not matter.
option_typeNoCE or PE, or CA or PA before 2011. Pass with strike.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses pagination shape (up to 250 rows, oldest first), the default date window, the historical coverage start (2010-01-04), market/segment limits, and an access-tier requirement with a link. These are exactly the operational facts 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?

Four tight sentences, front-loaded with the core purpose, then mode semantics, then defaults, then limits and access. No filler and no repetition of the title.

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 an 8-parameter read tool with no output schema, the description covers mode selection, defaults, row caps, ordering, data coverage, and auth tier. The only unaddressed area is the exact response shape, which is partially implied by the mention of IV and Greeks fields.

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 does not: the coupling of strike with option_type and the semantic difference between passing expiry alone versus with strike. It restates the from/to defaults, which the schema already documents, so it is not a full 5.

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?

"Daily history of one contract" names a specific verb and resource, and the next sentence disambiguates the two modes: expiry alone returns the future, expiry+strike+option_type returns that option with IV and Greeks. An agent can tell exactly what it will get 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?

It states the required parameters (symbol, expiry), the mode-selection rule, and scope exclusions (no BSE, no intraday, NSE equity derivatives only). It does not name a sibling to use instead for chains or futures lists, so routing to alternatives is left implicit.

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