Skip to main content
Glama
indian-option-mcp

indian-option-mcp

build_strategy

Create pre-defined options strategies such as Iron Condor or Bull Call Spread for Indian F&O symbols using real market prices and configurable strikes.

Instructions

Build a pre-defined options strategy (Iron Condor, Bull Call Spread, Straddle, etc.) with real market prices for an Indian F&O symbol.

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>",
      "strategy_name": "<strategy_name>"
    },
    "name": "build_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
expiryNoExpiry date
symbolYesUnderlying symbol
otm_offsetNoNumber of strikes away from ATM for OTM legs (default: varies by strategy)
strategy_nameYesStrategy name: iron_condor, bull_call_spread, short_straddle, long_straddle, bear_put_spread, etc. Use list_strategies to see all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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 burden. It mentions 'real market prices' as a behavioral trait but does not disclose whether the tool is read-only, what it returns, error handling, or any rate limits. Significant gaps remain for a tool that likely produces multi-leg strategy details.

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

Conciseness5/5

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

A single, front-loaded sentence that clearly states the tool's purpose with no unnecessary wording.

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?

Given no annotations, no output schema, and a moderate complexity (4 parameters), the description is too sparse. It omits what the tool returns, any constraints around expiry or symbol format, and usage context for Indian F&O symbols beyond the basic mention.

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%, so the schema already documents all four parameters. The description adds no additional meaning beyond the schema, but baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb 'Build' and resource 'pre-defined options strategy' with examples (Iron Condor, Bull Call Spread, Straddle). It distinguishes from a custom strategy by emphasizing 'pre-defined', though it does not explicitly name the sibling custom_strategy.

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 description implies usage for building pre-defined strategies but does not state when to use this tool versus alternatives like custom_strategy or suggest_strategy. No explicit exclusions or conditions are given.

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