Skip to main content
Glama
indian-option-mcp

indian-option-mcp

estimate_margin

Calculate the SPAN and Exposure margin required for an Indian options strategy by entering a symbol and option legs, helping you plan capital and assess trade feasibility.

Instructions

Estimate the margin required for an options strategy (SPAN + Exposure margin).

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>",
      "legs": "<legs>"
    },
    "name": "estimate_margin"
  }
}

Input Schema

NameRequiredDescriptionDefault
legsYes
symbolYes

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?

With no annotations, the description carries the full behavioral burden. It discloses the margin methodology (SPAN + Exposure), which is genuinely useful domain context, but says nothing about whether the estimate is broker-specific, whether it requires account/margin data, how precise the result is, or what the response contains (a single number vs. a SPAN/Exposure breakdown).

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 or redundancy; the parenthetical methodology is informative rather than padding. It is arguably too terse for a tool with a nested leg array, but there is no wasted wording to cut.

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 whose main input is a structured list of option legs and which produces a computed margin figure with no output schema, the definition omits leg construction guidance, symbol format, and result shape. An agent could not confidently construct a valid call from this description alone.

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 description coverage is 0% for two required parameters, and the nested 'legs' array alone has five subfields (type, strike, premium, action, qty) with no explanation. The description only implies that 'legs' describes strategy legs and that 'symbol' identifies the underlying; it gives no format or semantics for either, so it does not compensate for the coverage gap.

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 ('Estimate') and resource ('margin required for an options strategy') and adds the calculation basis (SPAN + Exposure margin), which distinguishes it from sibling calculators like calculate_greeks or calculate_payoff. It stops short of explicitly naming what it is not, but the purpose is unambiguous.

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 alternatives such as position_sizing or build_strategy, no prerequisites (e.g., needing an existing strategy or valid symbol/exchange), and no note on when margin estimation is not applicable. Usage must be inferred entirely from the name and one sentence.

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