Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Compute Ichimoku Kinko Hyo lines and future cloud

technical-analysis_ichimoku
Read-onlyIdempotent

Compute Tenkan, Kijun, displaced Senkou A/B and Chikou on caller-supplied OHLCV bars, plus the cloud projected beyond the last bar. Price $0.03 USDC. POST /api/v1/technical-analysis/ichimoku. 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_ichimoku"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
kijunNokijun, integer, from 1 to 20000. Required.
tenkanNotenkan, integer, from 1 to 20000. Required.
senkouBNosenkouB, integer, from 1 to 20000. Required.
displacementNodisplacement, integer, from 1 to 1000. Required.

Output Schema

NameRequiredDescriptionDefault
kijunNokijun. Array.
chikouNochikou. Array.
paramsNoparams. Object.
tenkanNotenkan. Array.
warmupNowarmup. Object.
senkouANosenkouA. Array.
senkouBNosenkouB. Array.
sourcesNosources. Array.
futureCloudNofutureCloud. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

The annotations already state readOnly, idempotent, non-destructive and open-world, so the description correctly spends its words elsewhere: it discloses the price ($0.03 USDC), the x402 payment requirement, the endpoint (POST /api/v1/technical-analysis/ichimoku), and the failure mode that an unpaid call returns payment terms without executing. That payment-gate behavior is invisible to the annotations and is exactly what an agent needs to avoid a silent no-op.

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 the computational scope, then cost/transport, then the failure case. No sentence is redundant and no filler precedes the substantive content.

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 not be explained, and the description covers scope, cost, transport and payment failure. The minor gap is the absence of any data-volume caveat — how many bars are needed for a valid cloud projection — which matters for a lookback-based indicator.

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%, and the schema already supplies defaults and bounds for tenkan, kijun, senkouB and displacement, so the baseline of 3 applies. The description adds only passing semantic colour — 'displaced Senkou A/B' and 'cloud projected beyond the last bar' — clarifying what displacement means behaviourally, but it never maps the named parameters to those roles.

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 a specific verb (Compute) and resource (Ichimoku Kinko Hyo: Tenkan, Kijun, displaced Senkou A/B, Chikou) and adds the distinguishing scope element — the cloud projected beyond the last bar. That is enough for an agent to separate it from sibling technical-analysis endpoints such as macd or moving-averages without opening 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 Guidelines3/5

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

Usage is only implied: the tool operates on 'caller-supplied OHLCV bars', so the agent knows the input precondition but is given no explicit when-to-use, when-not, or named alternative among the thirteen sibling indicator tools. It is adequate for a self-describing single-indicator endpoint but leaves selection to inference.

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