Skip to main content
Glama
indian-option-mcp

indian-option-mcp

get_pcr

Calculate the Put-Call Ratio for an Indian options symbol and expiry to gauge market sentiment using open interest, volume, and OI change.

Instructions

Calculate Put-Call Ratio (PCR) based on Open Interest, Volume, and OI Change.

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

Input Schema

NameRequiredDescriptionDefault
expiryNo
symbolYesSymbol

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. 'Calculate' implies a side-effect-free read, but the description does not say whether one blended ratio or three separate ratios are returned, what data source/underlying is used, or how it behaves when expiry is omitted — key gaps for a computation tool.

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, which is structurally clean. It is efficient but under-specifies rather than over-explains.

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, and half the parameters undocumented, the definition leaves too much open for an agent to call it confidently — notably what the return value looks like and how expiry changes 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?

Coverage is 50%, and the only documented parameter is symbol with the tautological label 'Symbol'. The description never mentions the expiry parameter at all, nor what format symbol or expiry should take, so it does not compensate for the schema 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 specific, well-known resource ('Put-Call Ratio (PCR)'), and names the three inputs it is derived from (Open Interest, Volume, OI Change). It does not differentiate itself from siblings such as oi_change_analysis or get_option_chain, so it stops short of a 5.

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 when-to-use guidance, no mention of prerequisites or alternatives, and no statement about whether an expiry is needed for a meaningful result. The agent must infer that this is the tool for aggregate put/call positioning purely from the name.

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