Skip to main content
Glama
indian-option-mcp

indian-option-mcp

oi_change_analysis

Analyze open interest changes across Indian option strikes to identify emerging support/resistance levels and gauge market sentiment.

Instructions

Analyze Change in Open Interest across strikes to identify emerging support/resistance and market sentiment.

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

Input Schema

NameRequiredDescriptionDefault
expiryNo
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/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 disclosure burden, and it omits key behavioral facts: over what window 'change' is measured (session, day, since previous close), whether it is computed from stored or live data, and what the response looks like. It does at least signal a read-only analytical operation implicitly.

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 operation front-loaded and no filler. It is efficient, though brevity here comes partly from omitting necessary detail rather than from tight editing.

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?

Even for a two-parameter tool with no output schema, the definition leaves out the change window, the meaning of the optional expiry, and any hint of the returned structure. An agent could invoke it but could not predict or interpret the result.

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 0% for both parameters, so the description must compensate and does not: 'symbol' (required) and 'expiry' (optional) are never mentioned. It also never explains whether expiry is mandatory for meaningful OI-change analysis or which date format is expected.

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 names a specific verb and resource ('Analyze Change in Open Interest across strikes') and adds the analytical goal (support/resistance, sentiment). It does not distinguish itself from plausible siblings like highest_oi_strikes or unusual_activity, so an agent cannot tell from the text which OI tool to pick.

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 by the stated goal of spotting emerging support/resistance and sentiment; there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the scenario rather than being routed to it.

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