Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Compute Fibonacci retracement and extension levels

technical-analysis_fibonacci-levels
Read-onlyIdempotent

Compute retracement and extension prices between a supplied swing low and high, or between the highest high and lowest low of caller-supplied bars. Price $0.02 USDC. POST /api/v1/technical-analysis/fibonacci-levels. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "technical-analysis_fibonacci-levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsNobars, array. Optional.
levelsNolevels, array. Required.
lookbackNolookback, integer, from 2 to 20000. Required.
swingLowNoswingLow, number. Optional.
directionNodirection, string, one of up, down. Required.up
swingHighNoswingHigh, number. Optional.
extensionsNoextensions, array. Required.

Output Schema

NameRequiredDescriptionDefault
paramsNoparams. Object.
warmupNowarmup. Object.
sourcesNosources. Array.
swingLowNoswingLow. Number.
directionNodirection. String.
swingHighNoswingHigh. Number.
extensionsNoextensions. Array.
limitationsNolimitations. Array.
retracementsNoretracements. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses pricing ($0.02 USDC), the POST endpoint, and crucially that an unpaid call returns x402 payment terms without running the computation. This adds important behavioral context not present in the readOnly/idempotent annotations.

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 sentences, front-loaded with the core operation, followed by price and payment behavior. No redundant or filler wording; every sentence carries useful 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?

The description covers the calculation modes, payment requirements, endpoint, and failure behavior for a tool with seven parameters and an existing output schema. It leaves the semantics of levels, extensions, direction, and lookback to the schema, which is acceptable given 100% schema coverage, though a brief note on their role would complete the picture.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful interpretation: swingLow and swingHigh define one calculation mode, while bars supplies OHLC data whose highest high and lowest low define the other. It does not explain levels, extensions, direction, or lookback, but the added mode semantics justify a 4.

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 states a specific verb (compute) and resource (Fibonacci retracement and extension prices) and distinguishes two precise input modes: a supplied swing low/high or the highest high and lowest low of caller-supplied bars. An agent can identify exactly what the tool returns without opening 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 Guidelines4/5

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

The description clearly explains the two ways to invoke the tool, effectively telling the caller when to supply swingHigh/swingLow versus bars. It does not compare against sibling technical-analysis tools or give exclusions, but the usage context is clear.

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