Skip to main content
Glama

index_option_chain

Retrieve an index's option chain with strike prices, open interest, and volumes for a chosen expiry. Analyze market sentiment and identify trading opportunities.

Instructions

Option chain for an index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expiryNo
symbolNoNIFTY
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as return format, data source, rate limits, or side effects. The sole phrase 'Option chain for an index' provides no information beyond the tool's name, so the description carries no transparency burden.

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

Conciseness2/5

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

The description is extremely short, but this is under-specification rather than effective conciseness. It omits all useful information and is merely a noun phrase, failing to provide a functional description that earns its place.

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

Completeness1/5

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

With no output schema, no annotations, and zero parameter documentation, the description is completely inadequate for a tool with 2 parameters. The agent has no basis for understanding inputs, outputs, or behavior, making the description contextually incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description does not mention either parameter ('expiry' or 'symbol'). Without any explanation of what these parameters represent or how they affect results, the agent cannot infer their meaning beyond the raw schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase, 'Option chain for an index,' which essentially restates the tool name 'index_option_chain' without any action verb. It does not distinguish the tool from siblings like equities_option_chain or currency_option_chain, as it lacks specific scope or purpose details.

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?

The description offers no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, leaving the agent unable to determine the appropriate situation compared to sibling tools such as option_chain_contract_info or index_pe_history.

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/jugaad-py/nse-mcp'

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