Skip to main content
Glama
indian-option-mcp

indian-option-mcp

probability_of_profit

Calculates the probability of profit for credit or debit options strategies using breakevens, spot price, implied volatility, and days to expiry.

Instructions

Calculate the Probability of Profit (POP) for an options strategy using log-normal distribution.

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": {
      "breakevens": "<breakevens>",
      "spot_price": "<spot_price>",
      "iv": "<iv>",
      "days_to_expiry": "<days_to_expiry>",
      "strategy_type": "<strategy_type>"
    },
    "name": "probability_of_profit"
  }
}

Input Schema

NameRequiredDescriptionDefault
ivYesIV as percentage
breakevensYesBreakeven price(s) of the strategy
spot_priceYes
strategy_typeYes
days_to_expiryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose the underlying model ('log-normal distribution'), which tells the agent the result is a model-based estimate rather than an empirical one. It does not state that the call is a pure stateless computation with no side effects, nor what assumptions or limitations the log-normal model imposes.

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 filler, so it is efficient and easy to scan. It is arguably too terse for a five-parameter quantitative tool, but nothing in it is wasted.

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 tool with five required parameters and no output schema, the description omits both parameter meaning and the shape of the result (a probability in percent or a 0-1 fraction). Given no annotations and no return schema, it leaves significant gaps an agent would need filled before calling it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40%: iv and breakevens are documented, but spot_price, days_to_expiry, and strategy_type are not. The description adds no meaning to any parameter, leaving the agent to guess, for example, that spot_price is the underlying's current price and that strategy_type selects the sign convention for POP.

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 uses a specific verb and resource ('Calculate the Probability of Profit (POP)') and names the domain ('options strategy'), which is enough to distinguish it from siblings like calculate_payoff or calculate_greeks. It does not explicitly contrast itself with those siblings, 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 scope is implied by 'for an options strategy', but there is no explicit when-to-use or when-not-to-use guidance, nor any pointer to a sibling such as calculate_payoff or expected_move for related questions. The agent must infer the trigger conditions.

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