Skip to main content
Glama
indian-option-mcp

indian-option-mcp

expected_move

Calculate the price range an underlying is likely to stay within by expiry using a chosen confidence level, so you can size trades and manage risk.

Instructions

Calculate the Expected Move — the price range the market expects the underlying to stay within by expiry.

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

Input Schema

NameRequiredDescriptionDefault
expiryNo
symbolYes
confidenceNoSigma multiplier: 1=68%, 1.645=90%, 1.96=95% (default: 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It explains the meaning of the metric but says nothing about data requirements, whether it is a pure read/computation, what happens when expiry is omitted, or what the response contains; 'by expiry' hints that an expiry matters but is not elaborated.

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?

A single sentence with the core concept front-loaded and no filler. It is efficient, though the terseness is partly why parameter and behavioral gaps remain.

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?

With three parameters, low schema coverage, no annotations, and no output schema, the definition should clarify the optional expiry behavior and the shape of the returned range. As written, an agent knows what the tool computes but not how to call it correctly in edge cases or what it will receive back.

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 coverage is only 33% — only 'confidence' is documented in the schema. The description adds nothing about 'symbol' format or about 'expiry' being optional and what default (presumably next expiry) applies, so a third of the parameters remain unexplained and the description fails to compensate for the coverage gap.

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 ('Calculate') and a precisely defined resource ('Expected Move'), and parenthetically defines the concept as the price range the market expects the underlying to stay within by expiry. That definition lets an agent distinguish it from calculate_greeks, calculate_iv, or probability_of_profit, though it never explicitly routes to or away from those siblings.

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 guidance on when to choose this tool over the many sibling calculators, nor any stated prerequisites (e.g. must an option chain be available, must expiry be valid). Usage is only implied by the tool name and the concept definition.

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