Skip to main content
Glama
Sign In
India Market MCP

India Market MCP

by icharshal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

estimate_margin

Estimate SPAN and exposure margin for option strategies to determine capital requirements.

Instructions

Estimate SPAN + Exposure margin for option strategies.

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

Input Schema

NameRequiredDescriptionDefault
lotsNo
strategyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior. It only states the estimation action, but does not mention authentication needs, rate limits, or whether the tool modifies any state. The description does not go beyond the obvious.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but lacks structure. It does not front-load key information or organize details. More content could be added without sacrificing conciseness.

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

Completeness1/5

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

Given two parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain return values, what 'SPAN + Exposure' means, or how the strategy parameter should be structured. The agent lacks essential context.

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

Parameters1/5

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

The input schema has two parameters (lots, strategy) with zero schema description coverage. The description does not explain their meaning, valid formats, or how to specify the strategy. The agent must guess based on parameter names alone.

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 clearly states it estimates SPAN + Exposure margin for option strategies, which is specific and actionable. However, it does not differentiate from sibling tools like calculate_greeks or build_strategy, missing an opportunity to clarify its unique role.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., for pre-trade margin estimation vs. actual margin calculation). The description lacks context about prerequisites or scenarios.

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

Deploy Server

Other Tools