Skip to main content
Glama
indian-option-mcp

indian-option-mcp

lot_size

Retrieve NSE F&O lot sizes for stocks and indices to calculate strategy costs, margin requirements, and position sizing accurately.

Instructions

Get the F&O lot size (number of shares per contract) for any NSE stock or index. Essential for calculating strategy costs, margin, and position sizing. Returns the current lot size as defined by NSE.

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": "lot_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesNSE F&O symbol, e.g. NIFTY (75), BANKNIFTY (30), RELIANCE, TATASTEEL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; 'Get' and 'Returns the current lot size as defined by NSE' do signal a read-only, single-value lookup and hint that values are exchange-defined and can change. It omits error behavior for invalid/unknown symbols and any auth or rate-limit context, so meaningful gaps remain.

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?

Three short sentences, front-loaded with the definition of the value returned; nothing is buried. The middle sentence is mildly promotional ('Essential for...') but still conveys useful domain context, so it mostly earns its place.

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

Completeness4/5

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

For a one-parameter lookup with no output schema, the description does state what comes back (the current NSE-defined lot size), which is the key missing piece structured data does not cover. Only failure modes and staleness/refresh expectations are absent.

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 the schema already supplies example symbols with their lot sizes, so the description need not restate parameter format. It only adds the scope phrase 'any NSE stock or index', which is a marginal contribution beyond the schema's example list.

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?

States a specific verb and resource ('Get the F&O lot size') and immediately defines the unit ('number of shares per contract') plus scope ('any NSE stock or index'), so an agent knows exactly what it retrieves. It does not name sibling tools like position_sizing or estimate_margin, so differentiation is left to the agent.

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 sentence 'Essential for calculating strategy costs, margin, and position sizing' implies when the value is useful, but it is motivational rather than directive. It never says when to call this versus position_sizing or estimate_margin, and gives no prerequisites or exclusion conditions.

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