Loading ToolBench

Reading the current corpus…

Indian-Option-MCP MCP server · C · ToolBench

Indian-Option-MCP

Model Context Protocol server for Indian options market analysis — real-time option chains, Greeks, strategy building, and payoff analysis for NSE/NFO derivatives. Works with Claude Desktop.

<=2025-11-25STDIO4 tools

68/100

Definition Quality83

Protocol Readiness32

SupportabilityNot measured-

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

The server defines 4 tools with clear action verbs and complete input schemas. Descriptions are present and reasonably detailed (avg ~120 chars), meeting the 10 - 1024 char baseline. However, output schemas are NOT documented anywhere in the visible code, critical gap per the rubric. Parameters are well-typed (string, number, enum for type in calculate_greeks) and include descriptions. No error handling or recovery guidance is visible. Security is sound (read-only ops, no secrets in params). The tools are well-named and composed (each does one thing). Naming follows verb_noun convention (get_*, calculate_*). Significant opportunity to document output schemas and add error handling guidance.

Tools (4)

calculate_greeksread onlysource verified83/100

Calculate all Option Greeks (Delta, Gamma, Theta, Vega, Rho) for a given option using Black-Scholes model.

get_expiry_datesread onlysource verified83/100

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.

get_option_chainread onlysource verified82/100

Get the complete option chain for an Indian F&O symbol (NIFTY, BANKNIFTY, RELIANCE, etc.) with strike prices, LTP, Open Interest, IV, volume, bid/ask for both calls and puts.

get_spot_priceread onlysource verified83/100

Get the current spot/underlying price of an Indian stock or index from NSE. Use this to check the latest price before calculating Greeks or building strategies. Returns spot price with timestamp.

Issues (4)

HIGHtool-response-shape ↗

Output schemas are not documented. The rubric requires that tools document what fields they return so LLMs can plan downstream calls and extract data correctly. No TypeScript return types or JSDoc @returns are visible in src/server.ts.

get_option_chainget_expiry_datesget_spot_pricecalculate_greeks

HIGHrecovery-guide ↗

No error recovery guidance. Tools return no actionable error messages. If get_option_chain fails (invalid symbol, API timeout), the LLM receives no hint about what to do next (e.g., 'Try list_indices() to find valid symbols'). Per pattern:recovery-guide, errors must guide the agent's next step.

get_option_chainget_expiry_datesget_spot_pricecalculate_greeks

MEDIUMconstrained-input ↗

Missing input validation and parameter constraints. calculate_greeks accepts 'iv' and 'rate' as numbers with no min/max bounds specified. LLMs could pass negative rates or impossible IV values. Descriptions should include ranges: 'iv (0 - 200% as a number; e.g., 15 for 15%)'.

Recommendations

Add JSDoc or TypeScript return type annotations to each tool. Example for get_option_chain: '{ underlyingValue: number, rows: [{ strikePrice: number, CE: { openInterest: number, iv: number, ltp: number }, PE: {...} }], timestamp: string }'.
For get_option_chain, document the filtered output structure in the response. Currently the code returns a readable ASCII table string, but LLMs need structured field names (strikePrice, CE.openInterest, CE.iv, PE.openInterest, etc.) to parse and reason about the data reliably.
Add explicit error handling with recovery hints. Example: 'If symbol not recognized, call get_expiry_dates() with the correct NSE symbol. Common symbols: NIFTY, BANKNIFTY, RELIANCE, TATASTEEL.'
For calculate_greeks, add numeric constraints to parameter descriptions: 'iv: Implied Volatility as a percentage (0 - 200; e.g., 15 for 15%)', 'rate: Risk-free rate in % (0 - 20; e.g., 7 for 7%)'.
Consider adding a list_symbols or get_supported_symbols tool to help LLMs discover valid NSE symbols and avoid invalid calls.
Document what LLMs should do if strike_range is 0 or negative in get_option_chain (does it return all strikes, or an error?). Add constraint to description: 'strike_range: 1 - 50 (default 10)'.

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

68/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	C	68	<=2025-11-25	v2