Skip to main content
Glama
indian-option-mcp

indian-option-mcp

what_if_greeks

Calculate how option Greeks change under hypothetical spot price, implied volatility, or time-to-expiry scenarios for Indian options.

Instructions

What-if scenario: Show how Greeks change under hypothetical spot price, IV, or time conditions.

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>",
      "iv": "<iv>",
      "days_to_expiry": "<days_to_expiry>",
      "type": "<type>"
    },
    "name": "what_if_greeks"
  }
}

Input Schema

NameRequiredDescriptionDefault
ivYesHypothetical IV %
spotYesHypothetical spot price
typeYesOption type
strikeYesStrike price
days_to_expiryYesHypothetical days to expiry

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 provided, so the description carries the entire behavioral burden, and it discloses very little: nothing about side effects, permissions, or whether a full pricing model is invoked. It also never says which Greeks are returned or in what shape, despite there being no output schema to fall back on.

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?

A single front-loaded sentence with no wasted words; the scenario framing comes first and the varied inputs follow. It is efficient, though it sacrifices some detail for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-parameter computation with no output schema, the description covers the inputs at a high level but leaves the return contract (which Greeks, units, per-shift vs single-point) undefined. It is adequate to select the tool but thin for invoking and interpreting it.

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 is already documented in the schema, and the description only echoes three of the five (spot, IV, time) without adding format or constraint detail. The baseline of 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 gives a specific verb-plus-resource ('Show how Greeks change') and scopes it to hypothetical spot/IV/time conditions, which distinguishes it from a plain Greeks calculation on live inputs. It does not name a sibling tool explicitly, so it stops short of a 5.

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 word 'What-if' and 'hypothetical' imply the usage context (scenario analysis rather than current-state Greeks), but the description never states when to prefer this over calculate_greeks or what conditions disqualify it. Usage is inferred rather than stated.

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