Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Compute OBV, A/D line, CMF, VWAP and volume SMA

technical-analysis_volume-indicators
Read-onlyIdempotent

Compute on-balance volume, the accumulation/distribution line, Chaikin Money Flow, session-anchored or cumulative VWAP and a volume SMA on caller-supplied OHLCV bars. Price $0.03 USDC. POST /api/v1/technical-analysis/volume-indicators. 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_volume-indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
cmfPeriodNocmfPeriod, integer, from 1 to 20000. Optional.
sessionTzNosessionTz, string. Required.America/New_York
vwapAnchorNovwapAnchor, string, one of session, none. Required.session
volumeSmaPeriodNovolumeSmaPeriod, integer, from 1 to 20000. Optional.

Output Schema

NameRequiredDescriptionDefault
cmfNocmf. Array.
obvNoobv. Array.
vwapNovwap. Array.
adLineNoadLine. Array.
paramsNoparams. Object.
warmupNowarmup. Object.
sourcesNosources. Array.
volumeSmaNovolumeSma. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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, so the safety bar is lower. The description adds genuinely non-obvious behavior: a fixed price of $0.03 USDC, the concrete POST endpoint, and the fact that an unpaid call returns x402 payment terms instead of executing — a failure mode an agent must know before calling.

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: capability first, then cost, then endpoint, then the payment-failure caveat. No redundant restatement of the title and nothing that could be cut without losing information.

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 and full schema coverage, the description needn't explain returns, and it covers the billing and auth-adjacent behavior that structured fields cannot. Gaps remain around input assumptions — bar ordering, minimum history required for the SMA/CMF periods, and behavior on insufficient data — which matter for a multi-indicator computation.

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 100%, so a baseline of 3 applies, but the description goes further by explaining what vwapAnchor actually means ("session-anchored or cumulative VWAP"), which the enum values alone don't convey. It leaves cmfPeriod, volumeSmaPeriod and sessionTz unelaborated, so it is not fully explanatory.

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 — OBV, A/D line, CMF, session/cumulative VWAP and volume SMA — over caller-supplied OHLCV bars. This clearly separates it from siblings like momentum-oscillators, moving-averages or volume-profile without requiring the schema to be opened.

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 the use case (technical analysis on caller-supplied bars) and the vwapAnchor choice gives a hint about which mode to pick, but it never states when to use this tool versus alternatives such as volume-profile, nor any prerequisites like minimum bar count. Usage is inferable rather than guided.

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