Skip to main content
Glama
indian-option-mcp

indian-option-mcp

calculate_payoff

Calculate option payoff and P&L at expiry across various underlying prices by defining legs, spot price, and lot size to evaluate strategy outcomes.

Instructions

Calculate the payoff/P&L at expiry for given option legs at various underlying prices.

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": {
      "legs": "<legs>",
      "spot_price": "<spot_price>",
      "lot_size": "<lot_size>"
    },
    "name": "calculate_payoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
legsYes
lot_sizeYesLot size
spot_priceYesCurrent spot price for range calculation

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 are supplied, so the description carries the full disclosure burden. Saying 'at expiry' usefully signals that time value and IV are ignored, but it says nothing about whether this is a pure computation with no side effects, how the underlying price range is derived from spot_price, or what the result looks like.

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. Its brevity is efficient, though it comes at the cost of the missing details flagged elsewhere rather than through padding.

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?

This is a computation tool with no output schema, no annotations, and a nested leg array, yet the description never explains the return structure (price/payoff points, P&L per leg, max profit/loss) or how the sampled price range is determined. For an agent trying to invoke and interpret the result, key information is missing.

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 coverage is 67%, and the description says 'given option legs at various underlying prices', which loosely links the legs array and spot_price to the computation. It adds no meaning for the per-leg fields (qty default of 1, action, premium) or for how spot_price defines the price range and step — gaps the nested schema leaves open.

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 pairs a specific verb (Calculate) with a specific resource (payoff/P&L at expiry) and scope (given option legs, across various underlying prices). This functionally distinguishes it from sibling calculators like calculate_greeks and calculate_option_price, though it never names them explicitly.

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 when-to-use or when-not-to-use guidance, no mention of alternatives such as calculate_option_price or probability_of_profit, and no stated prerequisites. The agent must infer that this is the expiry P&L profile tool from the phrasing alone.

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