Skip to main content
Glama
indian-option-mcp

indian-option-mcp

get_option_chain

Fetch strike-level call and put data for Indian F&O symbols—LTP, Open Interest, IV, volume, and bid/ask—to analyze option chains by expiry.

Instructions

Get the complete option chain for an Indian F&O symbol (NIFTY, BANKNIFTY, RELIANCE, etc.) with strike prices, LTP, Open Interest, IV, volume, bid/ask for both calls and puts.

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

Input Schema

NameRequiredDescriptionDefault
expiryNoExpiry date (DD-Mon-YYYY or YYYY-MM-DD). Defaults to nearest expiry.
symbolYesUnderlying symbol, e.g. NIFTY, BANKNIFTY, RELIANCE
strike_rangeNoNumber of strikes around ATM to include (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the shape of the returned data (fields for both calls and puts), which is genuinely useful with no output schema, but it says nothing about response size, rate limits, data staleness, behavior when the symbol or expiry is invalid, or whether market hours matter.

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?

A single front-loaded sentence with the core action first and the returned fields trailing as supporting detail; no filler. The parenthetical field list is dense but each item conveys real payload information.

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

Completeness3/5

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

For a three-parameter read tool with full schema coverage, the description is adequate, and listing returned fields partly compensates for the absent output schema. It is still thin on behavior an agent would want before calling, such as typical response size across strike ranges and failure modes.

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% and the schema already explains expiry formats, the symbol examples, and the strike_range default of 10. The description adds nothing about parameters beyond what the schema states, so the baseline 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?

Names a specific verb and resource ('Get the complete option chain') scoped to Indian F&O symbols and enumerates the payload fields (strike, LTP, OI, IV, volume, bid/ask for calls and puts). An agent knows exactly what it retrieves, though it never contrasts itself with data-oriented siblings like get_pcr or get_expiry_dates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance is given: nothing tells the agent to call get_expiry_dates first, when to prefer get_pcr or highest_oi_strikes, or when this tool is inappropriate. The only implied context is 'Indian F&O symbol', which is a domain constraint rather than usage guidance.

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