Skip to main content
Glama
indian-option-mcp

indian-option-mcp

calculate_max_pain

Calculate the Max Pain strike price for an Indian option symbol and expiry to identify where option buyers lose the most.

Instructions

Calculate the Max Pain strike price — the price at which option buyers lose the most money.

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": {
      "symbol": "<symbol>"
    },
    "name": "calculate_max_pain"
  }
}

Input Schema

NameRequiredDescriptionDefault
expiryNo
symbolYesSymbol, e.g. NIFTY

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/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 burden and it discloses very little. It does not say whether live option-chain data is fetched, whether the result covers a single expiry, whether the underlying data can be stale, or how failures behave for an invalid symbol/expiry.

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 tight sentence with the operation front-loaded and the definitional gloss earning its place. No filler, though it is also short enough that the missing usage and expiry context is noticeable.

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?

With no annotations, no output schema and an undocumented optional parameter, the definition does not tell the agent enough to call this correctly or interpret the result. It should state the required input, the role of expiry, and roughly what the returned value represents.

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 50%: symbol is documented with an example, but expiry has no type-level description and is absent from the description entirely. Since max pain is inherently computed per expiry, leaving that parameter unexplained is a meaningful gap the description should have closed.

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 and a specific computed quantity ("Calculate the Max Pain strike price") and defines it as the strike at which option buyers lose the most. That is a distinct resource the sibling list does not duplicate. It does not, however, say how it relates to neighbours like get_option_chain or calculate_payoff, which an agent may need to pick between.

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 versus pulling a raw chain, nor on prerequisites such as needing a valid expiry or an active market. The optional expiry parameter is not discussed at all, so the agent gets no cue that max pain is normally expiry-specific.

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