Skip to main content
Glama
indian-option-mcp

indian-option-mcp

calculate_option_price

Computes theoretical option price using Black-Scholes model for Indian options from spot, strike, expiry days, implied volatility, and option type (CE/PE).

Instructions

Calculate theoretical option price 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_option_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
ivYesIV as percentage
rateNoRisk-free rate % (default: 7)
spotYesUnderlying price
typeYesOption type
strikeYesStrike price
expiry_daysYesDays to expiry

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden. It says nothing about the model's assumptions (European exercise, dividend treatment), the units or format of the returned premium, precision, or that a missing 'rate' defaults to 7. For a calculation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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?

One short, front-loaded sentence with no filler; the model name is the key qualifier and appears immediately. It is efficient, though so terse that brevity becomes under-specification rather than economy.

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?

A six-parameter pricing tool with no output schema and no annotations needs the description to say what comes back (premium only? greeks too?) and to state the model's limits. The definition covers only the model name, which is insufficient for an agent to interpret the result correctly.

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%, so every parameter including the CE/PE enum and the rate default is already documented in the schema. The description adds no interpretation beyond the schema — no mention of what 'iv as percentage' means in practice or how expiry_days affects the result. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource ('Calculate theoretical option price') and pins down the pricing model (Black-Scholes), which clearly separates it from calculation siblings like calculate_greeks or calculate_iv. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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 guidance on when to use this tool versus calculate_greeks, calculate_iv, calculate_payoff, or what_if_greeks. The agent must infer from the name alone that this is the standalone premium calculator rather than a scenario or sensitivity tool. No prerequisites, no exclusions, no context about inputs like expiry_days.

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