Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Compute moving averages (SMA, EMA, WMA, DEMA, TEMA, HMA)

technical-analysis_moving-averages
Read-onlyIdempotent

Compute SMA, EMA (SMA-seeded), WMA, DEMA, TEMA and Hull moving averages on caller-supplied OHLCV bars, on close or another price source, with warm-up length per series. Price $0.02 USDC. POST /api/v1/technical-analysis/moving-averages. 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_moving-averages"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
typesNotypes, array. Required.
periodNoperiod, integer, from 1 to 20000. Required.
sourceNosource, string, one of o, h, l, c, hl2, hlc3. Required.c

Output Schema

NameRequiredDescriptionDefault
paramsNoparams. Object.
seriesNoseries. Object.
warmupNowarmup. Object.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, so safety is covered; the description goes further by disclosing a $0.02 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms and does not execute. That payment-gate behavior is exactly the kind of thing annotations cannot convey. It stops short of noting size limits or error behavior for oversized batches.

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 computation and its inputs, followed by cost and contract details. Endpoint path is the only borderline item, and it is useful for agents that must construct the request.

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 the description covers inputs, computation variants and the payment gate. What is missing is operational detail such as maximum bar count or behavior when period exceeds series length, minor for this otherwise well-covered tool.

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 coverage is 100%, so the schema already documents bars, types, period and source, giving a baseline of 3. The description adds real meaning with '(SMA-seeded)' for EMA and 'warm-up length per series', but does not clarify the ambiguous 'source' enum values like hl2/hlc3/ohlc4 or the interplay of period with each MA type.

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 opens with a specific verb plus a precisely enumerated resource: SMA, EMA (SMA-seeded), WMA, DEMA, TEMA and Hull averages over caller-supplied OHLCV bars. The variant list and seeding detail make it unmistakable against siblings like momentum-oscillators or macd, which compute different quantities.

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?

It implies context ('on caller-supplied OHLCV bars, on close or another price source') and states the payment precondition, but never says when an agent should pick this over, say, trend-indicators or macd, nor any when-not condition. Usage must be inferred from the math named.

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