Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Compute Bollinger, Keltner and Donchian bands

technical-analysis_bands-channels
Read-onlyIdempotent

Compute Bollinger Bands with %B and bandwidth, Keltner Channels and Donchian Channels on caller-supplied OHLCV bars. Price $0.03 USDC. POST /api/v1/technical-analysis/bands-channels. 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_bands-channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
keltnerNokeltner, object. Required.
donchianNodonchian, object. Required.
bollingerNobollinger, object. Required.

Output Schema

NameRequiredDescriptionDefault
paramsNoparams. Object.
warmupNowarmup. Object.
keltnerNokeltner. Object.
sourcesNosources. Array.
donchianNodonchian. Object.
bollingerNobollinger. Object.
limitationsNolimitations. Array.

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, open-world behavior, so the bar is lower. The description adds material context beyond them: the $0.03 USDC price, the POST endpoint, and the important fact that an unpaid call returns payment terms without running. It does not disclose what happens when the bar array is shorter than the configured period, which is the main behavioral unknown for a windowed computation.

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 tight sentences with the capability front-loaded, followed by cost and endpoint, then the payment-failure behavior. Nothing is redundant with the title and no sentence is padding.

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?

For a deterministic indicator computation with a full output schema, the description covers what is computed, what inputs are expected, cost, and the payment gating path. The remaining gap is edge-case behavior — insufficient bars for the chosen period and how defaults are applied — which an agent would need before calling confidently.

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% with nested defaults, so the schema already carries the parameter burden and a 3 is the baseline. The description contributes the meaning of 'bars' as OHLCV and clarifies that Bollinger additionally yields %B and bandwidth, but it never explains k, mult, atrPeriod, or the relationship between period and required bar length.

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 names a specific verb ('Compute') and three concrete resources (Bollinger Bands with %B and bandwidth, Keltner Channels, Donchian Channels) operating on caller-supplied OHLCV bars. That is far more specific than a generic 'compute indicators' claim and effectively separates it from siblings like volatility-measures or moving-averages, though it never explicitly contrasts itself with any of them.

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 implied rather than stated: the tool takes caller-supplied OHLCV bars and returns band overlays. There is no guidance on when to pick bands-channels over volatility-measures, nor any precondition such as a minimum bar count relative to the period settings. The one genuinely useful usage rule given is the payment gate — an unpaid call returns x402 terms and does not execute.

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