Skip to main content
Glama
Akhilgovind02

india-stock-mcp

get_options_chain

Retrieve the options chain for NSE F&O stocks and indices, including calls and puts with last price, open interest, implied volatility, and volume. Optionally specify expiry and strike range.

Instructions

Get F&O options chain for a stock or index: calls and puts around the ATM strike with last price, OI, OI change, IV, and volume. Works for NIFTY, BANKNIFTY, and F&O stocks like RELIANCE.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expiryNoOptional expiry in DD-Mon-YYYY format e.g. '16-Jun-2026'. Default: nearest expiry.
symbolYesNSE F&O symbol e.g. NIFTY, BANKNIFTY, RELIANCE, TCS
strike_rangeNoOptional +/- range in points around ATM strike to include
Behavior3/5

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

No annotations provided, so description carries full burden. It describes output fields but does not mention read-only nature, authentication requirements, or error cases when symbol is not F&O. Adequate but not thorough.

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?

Two sentences, efficient and front-loaded. No redundant information. Every word serves a purpose.

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?

No output schema, but description lists key returned fields (last price, OI, OI change, IV, volume). For a tool with 3 parameters and clear purpose, this is sufficient context.

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%, but description adds value: gives date format example for expiry and explains default behavior, and clarifies what strike_range does. This goes beyond schema descriptions.

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?

Description states verb (Get), specific resource (F&O options chain for a stock or index), and what it returns (calls/puts, specific fields). Clearly distinguishes from sibling tools which are for funds, fundamentals, quotes, etc.

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?

Explicitly says which symbols it works for (NIFTY, BANKNIFTY, F&O stocks like RELIANCE), implying scope. Does not explicitly state when not to use it, but context with siblings makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Akhilgovind02/india-stock-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server