Skip to main content
Glama
indian-option-mcp

indian-option-mcp

custom_strategy

Build a custom multi-leg options strategy by defining strikes, actions, quantities, and expiry for each leg.

Instructions

Build a custom multi-leg options strategy with specific strikes and actions.

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

Input Schema

NameRequiredDescriptionDefault
legsYesArray of strategy legs
expiryNo
symbolYesUnderlying symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3/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 it leaves the most important question unresolved: does 'build' place orders, save a strategy, or only construct a payoff/analysis object? It also omits permissions, validation rules, side effects, and supported strategy constraints. It discloses only that the strategy is multi-leg and configured by strikes and actions.

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?

The description is a single front-loaded sentence with no filler or repetition. It is concise and easy to parse, even though the overall definition is under-specified 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?

This is a complex options-strategy tool with no annotations and no output schema, so the description must carry more context. It identifies the purpose but omits execution-vs-construction behavior, return information, parameter formatting, validation constraints, and sibling-tool routing.

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 only moderate at 67%, and the description adds little beyond the schema. It mentions strikes and actions, but does not explain the expiry parameter (which lacks a schema description), quantity, CE/PE semantics, action semantics, or leg validation rules.

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 and resource: build a custom multi-leg options strategy. It also identifies the key configuration element, specific strikes and actions. However, it does not explicitly distinguish this from sibling tools such as build_strategy or suggest_strategy, 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 Guidelines3/5

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

The phrase 'custom ... with specific strikes and actions' implies this is for users who need exact leg-by-leg control rather than a suggested or prebuilt strategy. But it does not explicitly say when to use this versus build_strategy or suggest_strategy, nor does it state prerequisites or when not to use it.

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