Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Compute true range, ATR, NATR and historical volatility

technical-analysis_volatility-measures
Read-onlyIdempotent

Compute true range, Wilder ATR, NATR and annualised close-to-close historical volatility on caller-supplied OHLCV bars. Price $0.02 USDC. POST /api/v1/technical-analysis/volatility-measures. 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": "technical-analysis_volatility-measures"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
hvPeriodNohvPeriod, integer, from 2 to 20000. Required.
atrPeriodNoatrPeriod, integer, from 1 to 20000. Required.
annualizationNoannualization, number, from any to 100000. Required.

Output Schema

NameRequiredDescriptionDefault
hvNohv. Array.
trNotr. Array.
atrNoatr. Array.
natrNonatr. Array.
paramsNoparams. Object.
warmupNowarmup. Object.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is low; the description still adds real value by disclosing the price ($0.02 USDC), the exact endpoint, and the x402 behaviour that an unpaid call returns payment terms and does not execute. That unpaid-call behaviour is a non-obvious trait an agent must know to avoid treating a payment challenge as a failed computation. It does not, however, say anything about rate limits or response shape beyond what the output schema supplies.

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 what is computed, then cost/endpoint, then the gating behaviour. No filler, and each sentence carries information an agent needs.

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, return values need no explanation, and annotations cover the safety profile. The description covers purpose, cost, transport and the payment gate; only the relationship between window length and sufficient bar count is left implicit.

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

Parameters5/5

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

Schema description coverage is 100%, so the baseline would be 3; the description goes beyond that by specifying the volatility variant as close-to-close and annualised, which gives the annualization parameter concrete meaning (trading days factor), and by identifying the input as OHLCV bars, matching the nested bar object's fields.

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 verb (Compute) and enumerates the exact resources produced: true range, Wilder ATR, NATR and annualised close-to-close historical volatility, over caller-supplied OHLCV bars. That naming alone separates it from siblings such as moving-averages or momentum-oscillators without needing their schemas.

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 usage context is implied by the indicator set (volatility analysis on OHLCV bars), and the payment precondition is spelled out. However, it never states when to pick this over related siblings, nor any input requirements beyond 'caller-supplied bars' (e.g. minimum bar count relative to the periods).

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