Skip to main content
Glama
indian-option-mcp

indian-option-mcp

scan_high_oi

Identify option strikes with the highest open interest buildup to spot significant institutional positioning and support informed trading decisions.

Instructions

Find strikes with the highest Open Interest buildup — indicates significant institutional positioning.

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

Input Schema

NameRequiredDescriptionDefault
expiryNo
min_oiNoMinimum OI threshold
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.4/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, yet it only adds an interpretation ("institutional positioning"). It does not state that this is a read-only scan, how many strikes are returned, whether results are ranked, or how "buildup" is computed versus raw OI.

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 front-loaded sentence with no filler; the core action comes first. The trailing interpretive clause is mildly speculative but does not bloat the definition.

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 no annotations, no output schema, three parameters at low description coverage, and a near-duplicate sibling, the definition should say considerably more. An agent cannot predict the result shape, ranking behavior, or how to disambiguate from highest_oi_strikes.

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 33%: only min_oi has a description. The description never mentions symbol (required), expiry, or min_oi, and gives no format hints (e.g. expiry string format, units for the OI threshold), so it 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Find strikes with the highest Open Interest buildup" gives a specific verb and resource, so the basic intent is legible. However, a sibling named highest_oi_strikes exists, and the description makes no attempt to distinguish "OI buildup" scanning from that tool, leaving the agent unable to tell which to call.

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 this tool should be chosen over oi_change_analysis, highest_oi_strikes, or unusual_activity. No preconditions (e.g. need an expiry first), no exclusions, and no indication of what happens if expiry is omitted.

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