Skip to main content
Glama

BRAINIAC Options Analytics

Compute IV rank and IV percentile

options-analytics_iv-rank-percentile
Read-onlyIdempotent

Compute IV rank and IV percentile of the current implied volatility against caller-supplied history over a trailing window of observations. Price $0.02 USDC. POST /api/v1/options-analytics/iv-rank-percentile. 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": {
      "current": "<current>",
      "history": "<history>"
    },
    "name": "options-analytics_iv-rank-percentile"
  }
}

Input Schema

NameRequiredDescriptionDefault
currentYescurrent, number. Required.
historyYeshistory, array. Required.
windowDaysNowindowDays, integer, from 5 to 2520. Required.

Output Schema

NameRequiredDescriptionDefault
maxNomax. Number.
minNomin. Number.
modelNomodel. String.
ivRankNoivRank. Number.
windowNowindow. Object.
currentNocurrent. Number.
sourcesNosources. Array.
rankNoteNorankNote. Null.
inputsUsedNoinputsUsed. Object.
limitationsNolimitations. Array.
ivPercentileNoivPercentile. Number.
observationsNoobservations. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavior: the $0.02 USDC price, the POST endpoint, and most importantly that an unpaid call returns x402 payment terms and does not execute — context an agent cannot get from annotations or schema.

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?

Three short sentences, front-loaded with the operation and then the cost and payment semantics; nothing is redundant or padded.

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?

With an output schema present the description need not explain return values, and it covers cost and payment failure modes that the schema cannot. The remaining gap is that it never defines the distinction between IV rank and IV percentile or states the minimum observation count needed for a meaningful result.

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 100%, so the baseline is 3. The description adds only light meaning — that 'history' is caller-supplied and the window is trailing observations — without clarifying how current/history/windowDays interact or how rank differs from percentile.

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 gives a concrete verb plus resource ('Compute IV rank and IV percentile of the current implied volatility against caller-supplied history') and scopes it with the trailing window, so an agent can tell this apart from solve-style siblings like implied-volatility-solve or historical-volatility. The only thing keeping it from a 5 is that it never names or contrasts a sibling explicitly.

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: 'caller-supplied history' tells the agent it must bring its own observations rather than have the tool fetch a series. There is no explicit when-to-use versus when-to-use-an-alternative statement, and no precondition guidance beyond the payment rule.

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