Skip to main content
Glama
indian-option-mcp

indian-option-mcp

calculate_greeks

Calculates all option Greeks—Delta, Gamma, Theta, Vega, and Rho—for Indian options using the Black-Scholes model, helping assess price sensitivity and risk.

Instructions

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

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

Input Schema

NameRequiredDescriptionDefault
ivYesImplied Volatility as percentage, e.g. 15 for 15%
rateNoRisk-free rate in % (default: 7% for India)
spotYesCurrent underlying price
typeYesOption type: CE (Call) or PE (Put)
strikeYesOption strike price
expiry_daysYesDays to expiry

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the pricing model (Black-Scholes), which is meaningful behavioral context. However, it omits key assumptions and limits such as European-style exercise, dividend treatment, and what happens with zero or negative days to expiry, and it says nothing about error behavior.

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 front-loaded sentence that enumerates the computed outputs and the model with no filler. Nothing in it is redundant.

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?

With no output schema, the description must signal returns, and it does so by naming all five Greeks. It stops short of stating the shape of the result (per-unit values, decimal vs percentage) or failure modes, which leaves a small but real gap for a pure-computation tool.

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 (spot, strike, expiry_days, iv, rate, type) already carries its meaning and units, including the India 7% rate default. The description adds no syntax, unit, or edge-case detail beyond that, so the baseline of 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?

Names a specific verb (calculate), a specific resource (all five Option Greeks) and the method used (Black-Scholes), so the operation is unambiguous. It does not differentiate itself from the sibling what_if_greeks, which an agent could easily confuse with this tool.

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?

There is no statement of when to use this versus what_if_greeks, calculate_option_price, or calculate_iv, nor any prerequisites or exclusions. The agent must infer the intended context 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.