Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Compute ADX/DMI, Parabolic SAR, Aroon and SuperTrend

technical-analysis_trend-indicators
Read-onlyIdempotent

Compute Wilder ADX with +DI/-DI, Parabolic SAR with trend, Aroon Up/Down and SuperTrend with direction on caller-supplied OHLCV bars. Price $0.04 USDC. POST /api/v1/technical-analysis/trend-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_trend-indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
sarNosar, object. Required.
barsYesbars, array. Required.
adxPeriodNoadxPeriod, integer, from 1 to 20000. Required.
supertrendNosupertrend, object. Required.
aroonPeriodNoaroonPeriod, integer, from 1 to 20000. Required.

Output Schema

NameRequiredDescriptionDefault
adxNoadx. Array.
sarNosar. Array.
paramsNoparams. Object.
plusDINoplusDI. Array.
warmupNowarmup. Object.
aroonUpNoaroonUp. Array.
minusDINominusDI. Array.
sourcesNosources. Array.
sarTrendNosarTrend. Array.
aroonDownNoaroonDown. Array.
supertrendNosupertrend. Array.
limitationsNolimitations. Array.
supertrendDirNosupertrendDir. 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?

Beyond the readOnly/idempotent/destructive=false annotations, the description discloses price ($0.04 USDC), the POST endpoint, and — importantly — that an unpaid call returns x402 payment terms and does not execute. That failure-mode disclosure is genuinely useful context that annotations do not cover. It stops short of mentioning rate limits or latency, so a 4 rather than a 5.

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 payment failure behavior. No filler or redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a read-only computation over caller-supplied input with a full output schema, so return-value details are unnecessary. Nested parameter objects are covered by the schema, and the payment/execution caveat covers the main non-obvious risk. Nothing essential to calling it correctly is missing.

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 the baseline is 3; however the description adds meaning by decoding 'bars' as OHLCV, which the schema only labels as opaque single-letter fields (t, o, h, l, c, v). It says nothing about adxPeriod, aroonPeriod, or the sar/supertrend tuning objects, so it does not fully compensate for the abbreviated schema wording.

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?

The description names the exact indicators computed — Wilder ADX with +DI/-DI, Parabolic SAR with trend, Aroon Up/Down, and SuperTrend with direction — on caller-supplied OHLCV bars. That specificity (indicator family plus outputs) separates it from siblings such as volatility-measures, momentum-oscillators and bands-channels without requiring the agent to open the schema.

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 OHLCV bars' tells the agent it must supply its own bar data, and the indicator list hints at trend-following analysis. There is no explicit when-to-use versus a sibling (e.g. when to pick this over moving-averages or momentum-oscillators), and no stated minimum bar count or data prerequisites.

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