Skip to main content
Glama
indian-option-mcp

indian-option-mcp

position_sizing

Calculate the right number of lots from capital, risk percentage, lot size, and maximum loss per lot to keep each trade within your risk limit.

Instructions

Calculate optimal position size based on capital and risk tolerance.

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": {
      "capital": "<capital>",
      "risk_percent": "<risk_percent>",
      "max_loss_per_lot": "<max_loss_per_lot>",
      "lot_size": "<lot_size>"
    },
    "name": "position_sizing"
  }
}

Input Schema

NameRequiredDescriptionDefault
capitalYesTotal trading capital in ₹
lot_sizeYesLot size of the instrument
risk_percentYesMax % of capital to risk per trade (e.g. 2)
max_loss_per_lotYesMaximum loss per lot for the strategy in ₹

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?

With no annotations, the description carries the full behavioral burden and discloses very little. It does not explain the calculation method, assumptions, rounding, whether the result is in lots or units, or what happens with invalid risk parameters. For a calculation tool with no output schema, this is a significant gap.

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?

The description is a single efficient sentence with the main concept front-loaded and no filler. It is appropriately concise, though its brevity contributes to the missing behavioral detail assessed elsewhere.

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 four-parameter calculation tool with no annotations and no output schema, the description is under-specified. It never states what the return value represents, how the calculation is performed, or what constraints apply to the inputs, leaving the agent to infer behavior.

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 description coverage is 100%, and every parameter is documented with type and meaning, including currency units. The description adds only a high-level framing (capital and risk tolerance) beyond the schema, which is appropriate but not materially informative above the schema baseline.

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 optimal position size." It also names the core inputs (capital, risk tolerance), making the purpose clear. It does not distinguish this tool from sizing-adjacent siblings such as lot_size or estimate_margin, so it falls 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives. The agent can infer that this is for trade sizing, but the description provides no routing help among the sizing and margin tools.

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