Skip to main content
Glama
Sign In
India Market MCP

India Market MCP

by icharshal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_option_chain

Get the full option chain for any NSE F&O symbol. Optionally filter by expiry date in DD-Mon-YYYY format.

Instructions

Get full option chain for NSE F&O symbol. Expiry format: DD-Mon-YYYY

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
expiryNo
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only gives the expiry format ('DD-Mon-YYYY') but does not mention auth requirements, rate limits, error handling (e.g., invalid symbol), or side effects. The format is parameter-level, not behavioral.

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?

The description is a single sentence plus a format note, both front-loaded. Every word contributes meaning without redundancy. Ideal conciseness for an AI agent to parse quickly.

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

Completeness2/5

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

Given the complexity of option chain data and no output schema, the description should hint at return fields (e.g., strikes, bid/ask, OI). It does not. Also lacks guidance on output structure or pagination. Incomplete for a data retrieval tool with zero schema coverage.

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?

Despite 0% schema coverage, the description adds the expiry format 'DD-Mon-YYYY', which is helpful for the 'expiry' parameter. However, it does not clarify the 'symbol' parameter (assumed NSE F&O symbol) or explain the default behavior when 'expiry' is empty (e.g., returns all expiries?). Partial compensation but incomplete.

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?

The description clearly states the verb 'Get', resource 'full option chain', and scope 'NSE F&O symbol'. It effectively distinguishes from sibling tools like get_futures_data (futures) and get_expiry_dates (only expiry dates). The term 'full option chain' implies comprehensive data, making the purpose unambiguous.

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 guidance is provided on when to use this tool versus alternatives like get_expiry_dates or get_oi_data. The description lacks any context about prerequisites, preferred usage scenarios, or exclusion criteria, leaving the agent to infer from the name alone.

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

Deploy Server

Other Tools