Skip to main content
Glama

BRAINIAC Options Analytics

Compute realised volatility from OHLC bars

options-analytics_historical-volatility
Read-onlyIdempotent

Compute close-to-close, Parkinson, Garman-Klass, Rogers-Satchell and Yang-Zhang realised volatility from OHLC bars, optionally excluding flagged days and returning a rolling series. Price $0.04 USDC. POST /api/v1/options-analytics/historical-volatility. 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": {
      "bars": "<bars>"
    },
    "name": "options-analytics_historical-volatility"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
windowNowindow, value. Optional.
estimatorsNoestimators, array. Required.
annualizationNoannualization, integer, from 1 to 366. Required.

Output Schema

NameRequiredDescriptionDefault
modelNomodel. String.
rollingNorolling. Null.
sourcesNosources. Array.
excludedNoexcluded. Number.
parkinsonNoparkinson. Number.
inputsUsedNoinputsUsed. Object.
yang_zhangNoyang_zhang. Number.
limitationsNolimitations. Array.
garman_klassNogarman_klass. Number.
observationsNoobservations. Number.
close_to_closeNoclose_to_close. Number.
rogers_satchellNorogers_satchell. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is not needed to establish safety; instead it adds materially new behavior: a $0.04 USDC charge, the concrete endpoint, and the crucial failure mode that an unpaid call returns x402 payment terms without executing. That payment gating is exactly the kind of context an agent cannot infer from annotations.

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?

Two sentences, front-loaded with the compute capability and estimator list, then the commercial/transport details. Every clause carries information; no padding or restatement of the title.

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, endpoint, and the unpaid-call path. Remaining gaps are minor: annualization behavior, the null-window default, and what happens with malformed bars are unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so baseline is 3, but the description adds real meaning by explaining that days can be flagged and excluded and that output can be a rolling series, which clarifies the purpose of the `exclude` flag and `window` parameter beyond their terse schema text.

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?

Names a specific verb and resource ('Compute ... realised volatility from OHLC bars') and enumerates the five estimators, which immediately separates it from siblings that price options or solve implied volatility. The scope modifiers (day exclusion, rolling series) further pin down what this tool produces.

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 description implies when this applies (you have OHLC bars and want realised rather than implied volatility), and it names the optional exclusion and rolling-series modes. But it never states when to choose this over the implied-volatility or surface-fit siblings, nor any input prerequisites or caveats.

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