Skip to main content
Glama
indian-option-mcp

indian-option-mcp

unusual_activity

Detect strikes with abnormally high options volume relative to open interest to spot unusual trading. Set symbol, optional expiry, and volume/OI threshold.

Instructions

Detect unusual options activity — strikes with abnormally high volume relative to open interest.

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

Input Schema

NameRequiredDescriptionDefault
expiryNo
symbolYes
thresholdNoVolume/OI ratio threshold (default: 0.5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the detection logic (volume relative to open interest), but says nothing about data recency, scope of the scan across expiries, what the response contains, or whether it is a pure read.

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?

A single tight sentence with the defining criterion front-loaded and no wasted words. It communicates the core concept immediately.

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 output schema and no annotations, the description should explain what a result looks like (list of strikes with volume, OI, ratio) and how expiry scoping works. Those gaps make it incomplete for a three-parameter screening tool with low schema coverage.

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 threshold is documented in the schema. The description alludes to the volume/OI ratio that threshold controls but gives no default or unit guidance in the description, and neither symbol nor expiry is explained beyond their obvious names.

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 ("Detect") and resource ("unusual options activity") and even defines the signal as strikes with abnormally high volume relative to open interest. It does not distinguish itself from nearby analytical siblings such as scan_high_oi or oi_change_analysis, which also surface strike-level volume/OI data.

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 explicit statement of when to use this tool versus alternatives, no exclusions, and no prerequisites. Usage is only implied by the phrase "detect unusual activity," leaving the agent to infer that it screens the chain rather than, say, fetching raw data.

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