Skip to main content
Glama

BRAINIAC Options Analytics

Compute max pain and open-interest walls

options-analytics_max-pain-oi
Read-onlyIdempotent

Compute the max-pain strike, per-strike payout, put/call open-interest ratio and the highest open-interest call and put walls for one expiry from a supplied option chain. Price $0.02 USDC. POST /api/v1/options-analytics/max-pain-oi. An unpaid call returns the x402 payment terms and does not run.

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": {
      "chain": "<chain>"
    },
    "name": "options-analytics_max-pain-oi"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYeschain, array. Required.
topWallsNotopWalls, integer, from 1 to 50. Required.
multiplierNomultiplier, number. Required.

Output Schema

NameRequiredDescriptionDefault
modelNomodel. String.
maxPainNomaxPain. Number.
sourcesNosources. Array.
putWallsNoputWalls. Array.
callWallsNocallWalls. Array.
inputsUsedNoinputsUsed. Object.
limitationsNolimitations. Array.
painByStrikeNopainByStrike. Array.
putCallOiRatioNoputCallOiRatio. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely non-obvious behavior: a price of $0.02 USDC and the x402 payment-terms failure mode where an unpaid call does not execute the computation. Rate limits and the meaning of 'walls' are still unstated, keeping it below a 5.

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?

Front-loaded with the computation and its outputs, then cost, then endpoint, then the payment failure mode — a sensible order with no filler. It is dense rather than padded, though the raw HTTP path and price are metadata that could be trimmed for an agent already reading structured fields.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the description covers cost and the unpaid-call behavior that an agent must plan around. Remaining gaps are modest: what defines a 'wall' (top N by OI is implied by topWalls), whether the chain must be sorted, and how multiplier affects payout — none of which would block a correct call.

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 description coverage is 100%, so each of chain, topWalls and multiplier is already documented, and the baseline of 3 applies. The description adds light semantics by framing chain as an option chain for a single expiry and tying topWalls implicitly to the 'highest open-interest walls' output, but multiplier (contract size, default 100) is never explained and no item-level expectations beyond the schema are given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific set of computed outputs (max-pain strike, per-strike payout, put/call OI ratio, highest OI call and put walls) against a specific resource (one expiry of a supplied option chain). That is clearly distinguishable from the sibling greeks/IV/skew/parity tools, which compute different quantities.

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?

The phrase 'for one expiry from a supplied option chain' implies the caller must already hold the chain data, which is useful context. But there is no explicit when-to-use/when-not guidance and no routing to or away from any sibling tool, so the agent must infer fit from the name and output list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources