Skip to main content
Glama
Sign In
vikalp

vikalp

by biranjan01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

max_pain

Compute max pain, PCR, and CE/PE walls from a live NSE option chain to identify key support and resistance levels for an underlying.

Instructions

Max pain, PCR and CE/PE walls for an underlying's live option chain.

Fetches the public NSE snapshot in-session (may be rate-limited; retry once after a pause if it fails).

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

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavioral traits: the snapshot is fetched from public NSE in-session and may be rate-limited, with a retry recommendation. However, it omits read-only status, permission/auth needs, latency, and failure modes beyond rate limiting.

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?

Two tight sentences with the payload front-loaded; the second sentence adds operational value rather than filler. Nothing is wasted, though the parenthetical could be slightly more compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There are no annotations and no output schema, so the description must compensate more than it does. It names the three output metrics and flags rate limiting, but never explains the response shape, units, or behavior when the chain is unavailable.

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 0% for the single required 'symbol' parameter, so the description is the only source of meaning. 'For an underlying's' implies symbol is the underlying instrument, but it never states the required format (e.g., NSE ticker conventions), leaving a real 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?

Names specific outputs (max pain, PCR, CE/PE walls) for a specific resource (an underlying's live option chain), so the agent knows what it computes. It does not distinguish itself from the sibling option_chain, which likely overlaps heavily.

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 when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The agent must infer that this is the tool for max-pain/PCR analytics versus the broader option_chain.

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

Deploy Server

Other Tools