Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Compute momentum oscillators (RSI, Stochastic, CCI, MFI)

technical-analysis_momentum-oscillators
Read-onlyIdempotent

Compute Wilder RSI, Stochastic %K/%D, Williams %R, CCI, ROC and MFI on caller-supplied OHLCV bars, with warm-up length per series. Price $0.03 USDC. POST /api/v1/technical-analysis/momentum-oscillators. 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_momentum-oscillators"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
stochDNostochD, integer, from 1 to 20000. Required.
stochKNostochK, integer, from 1 to 20000. Required.
cciPeriodNocciPeriod, integer, from 1 to 20000. Required.
mfiPeriodNomfiPeriod, integer, from 1 to 20000. Required.
rocPeriodNorocPeriod, integer, from 1 to 20000. Required.
rsiPeriodNorsiPeriod, integer, from 1 to 20000. Required.
indicatorsNoindicators, array. Required.
williamsPeriodNowilliamsPeriod, integer, from 1 to 20000. Required.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a $0.03 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms instead of running. It stops short of saying what happens with insufficient bars or how defaults are applied.

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: capability first, then price and endpoint, then the failure mode. Nothing is redundant and the most important information is front-loaded.

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?

An output schema exists, so return values need no explanation, and payment/auth behavior is disclosed. For a 9-parameter indicator bundle the remaining gap is modest: no guidance on minimum bar count relative to the largest period, or on which indicators run when the indicators array is left at its default.

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 baseline is 3 and the schema already documents every period parameter and the indicator enum. The description contributes one extra idea, that periods act as warm-up length per series, and clarifies bars are caller-supplied OHLCV, but adds no format or ordering detail for the bars array.

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?

Names a specific verb (compute) and resource (momentum oscillators), then enumerates the exact indicators produced: Wilder RSI, Stochastic %K/%D, Williams %R, CCI, ROC, MFI. That enumeration is what separates it from siblings like technical-analysis_macd or technical-analysis_trend-indicators without the agent needing to open a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says what it computes but never states when to reach for this tool versus the other technical-analysis siblings, nor any precondition such as a minimum number of bars needed for the requested periods. The only situational guidance is about payment, not about tool selection.

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