Skip to main content
Glama
indian-option-mcp

indian-option-mcp

highest_oi_strikes

Find strikes where open interest concentrates to spot Put OI support and Call OI resistance levels for Indian options.

Instructions

Find strikes with highest Open Interest — these act as support (Put OI) and resistance (Call OI) levels.

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

Input Schema

NameRequiredDescriptionDefault
top_nNoNumber of top strikes to show (default: 5)
expiryNo
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/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 does not meet it. It never states whether an expiry is required or defaulted to the nearest, how many results come back by default, whether OI is aggregated per strike across expiries, or what the response contains — only the analytic interpretation of the numbers is explained.

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 tight sentence with the core purpose front-loaded and no filler. The em-dash clause adds interpretive value rather than padding, though it consumes space that could have covered parameter behavior.

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?

For a 3-parameter tool with no annotations and no output schema, this is thin. The critical open question — how expiry is treated when omitted, and what the returned strike set looks like — is unanswered, so an agent must guess before calling.

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 coverage is 33%: only top_n has a schema description, while symbol and expiry are bare. The description adds no meaning to any parameter — it doesn't say whether expiry is optional, what happens if omitted, or what symbol formats are accepted. The one documented parameter's default is already in the schema.

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 gives a specific verb and resource ('Find strikes with highest Open Interest') and adds the interpretive meaning of the result (Put OI = support, Call OI = resistance). It does not, however, distinguish itself from the sibling scan_high_oi, which by name appears to target the same concept.

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?

Usage is only implied: the mention of support/resistance levels suggests the tool is for identifying key price levels, but there is no explicit statement of when to use this versus scan_high_oi or oi_change_analysis. No prerequisites or exclusions are given.

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