Skip to main content
Glama
indian-option-mcp

indian-option-mcp

next_expiry

Retrieve the next upcoming F&O expiry date for an Indian stock or index, including weekly index and monthly contracts, to determine time-to-expiry for Greeks calculations and strategy timing.

Instructions

Get the next upcoming F&O expiry date for an Indian stock or index. Supports both weekly (index) and monthly expiries. Use to determine time-to-expiry for Greeks calculations or strategy timing.

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": "next_expiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesNSE F&O symbol, e.g. NIFTY, BANKNIFTY, RELIANCE
weeklyNoIf true, get weekly expiry (only indices have weekly)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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 behavioral burden. It discloses the weekly-versus-monthly expiry distinction and that weekly applies only to indices, but says nothing about return shape (a date string?), how the next expiry is chosen around holidays, or what happens if weekly=true is passed for a stock symbol.

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?

Three short sentences, front-loaded with the core purpose, with no filler. The middle sentence largely duplicates the schema's weekly/indices note, which is the only minor redundancy.

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 two-parameter lookup with a fully documented schema and no annotations or output schema, the description covers purpose, scope, and the weekly/monthly nuance adequately. The missing piece is what the call returns and error behavior for invalid or non-F&O symbols.

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 both parameters are already documented, including the example NSE symbols and the 'only indices have weekly' caveat. The description restates that caveat without adding format, defaults, or edge-case behavior, so it hovers at the baseline for a fully described schema.

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: 'Get the next upcoming F&O expiry date' scoped to Indian stocks or indices, and clarifies single-next-date versus a range. It does not distinguish itself from the sibling get_expiry_dates, which plausibly returns a full list, so an agent must infer the difference from the names alone.

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

Usage Guidelines3/5

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

The description gives usage context ('determine time-to-expiry for Greeks calculations or strategy timing'), which is real guidance on when to reach for it. It stops short of any exclusion or named alternative, so an agent choosing between this and get_expiry_dates, or between this and calculate_greeks directly, gets no routing help.

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