Skip to main content
Glama
indian-option-mcp

indian-option-mcp

get_expiry_dates

Fetch all available F&O expiry dates for an Indian stock or index, returned as a chronological numbered list to help you pick weekly or monthly expiries before building strategies.

Instructions

Get all available F&O expiry dates for an Indian stock or index. Use to find weekly/monthly expiries before building strategies. Returns a numbered list of expiry dates sorted chronologically.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesNSE underlying symbol, e.g. NIFTY, BANKNIFTY, RELIANCE, TATASTEEL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; it does add useful return-shape information (a numbered, chronologically sorted list), which goes beyond the schema. It says nothing about invalid symbols, empty results, or whether expiries include both weekly and monthly in one list versus filtering.

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?

Three short sentences with zero padding: purpose, use case, return format, in that order. Nothing is repeated from the name and nothing is wasted.

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?

For a one-parameter read tool with no output schema, the description covers purpose, use case, and the shape of the returned list, which is close to sufficient. A note on behavior for unknown symbols or on weekly-vs-monthly ordering within the list would close the remaining gap.

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 coverage is 100% and the single symbol parameter is fully documented in-schema. The description adds only the qualifier 'Indian stock or index,' which loosely reinforces the NSE scope but adds no format or edge-case meaning beyond the schema. 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?

States a specific verb and resource: retrieve F&O expiry dates for an Indian stock or index, with scope clarified as weekly/monthly. The 'all available' wording implicitly contrasts with a nearest-expiry sibling, but that sibling (next_expiry) is never named, so differentiation still requires inference.

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 to use it 'to find weekly/monthly expiries before building strategies,' which gives a clear invocation context. It stops short of naming alternatives or stating when another tool (e.g., the next-expiry one) is the better choice.

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