Skip to main content
Glama
indian-option-mcp

indian-option-mcp

calculate_iv

Compute implied volatility for Indian options from market price, spot, strike, expiry, and type using the Newton-Raphson method.

Instructions

Calculate Implied Volatility from the market price of an option using Newton-Raphson method.

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": {
      "market_price": "<market_price>",
      "spot": "<spot>",
      "strike": "<strike>",
      "expiry_days": "<expiry_days>",
      "type": "<type>"
    },
    "name": "calculate_iv"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNoRisk-free rate % (default: 7)
spotYesUnderlying spot price
typeYesOption type
strikeYesStrike price
expiry_daysYesDays to expiry
market_priceYesCurrent market premium of the option

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/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. Naming Newton-Raphson is genuinely useful because it signals an iterative numerical solver, but the description never discloses what happens on non-convergence, whether a tolerance or iteration cap exists, or what the call returns — significant gaps for a solver that can fail on bad inputs.

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?

A single well-formed sentence with the core action front-loaded and zero filler. Nothing could be removed without losing information.

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?

For a six-parameter numerical solver with five required inputs, no annotations, and no output schema, the description is too thin. An agent gets no information about the return value (a volatility figure and its units), convergence failure behavior, or input validity constraints, all of which matter for correct invocation.

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 description coverage is 100% and every parameter including the rate default is documented in the schema, so the baseline of 3 applies. The description adds no domain meaning beyond the schema — it does not explain units, acceptable ranges, or that expiry_days must be positive.

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?

The description states a specific verb and resource — 'Calculate Implied Volatility from the market price of an option' — and even names the numerical method used, so the inverse relationship to a pricing tool is inferable. It stops short of explicitly contrasting itself with calculate_option_price, which is the nearest sibling.

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?

Usage is implied by the phrasing 'from the market price of an option', which tells the agent the required input precondition. There is no explicit when-to-use/when-not guidance, no mention of alternatives such as calculate_option_price for the forward direction, and no stated preconditions like valid arbitrage-consistent pricing.

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