Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Cluster support and resistance zones

technical-analysis_support-resistance
Read-onlyIdempotent

Cluster swing highs and lows of caller-supplied bars into horizontal support and resistance zones with touch counts. Price $0.03 USDC. POST /api/v1/technical-analysis/support-resistance. 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_support-resistance"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
minTouchesNominTouches, integer, from 1 to 1000. Required.
swingWindowNoswingWindow, integer, from 1 to 500. Required.
zoneWidthPctNozoneWidthPct, number, from any to 1. Required.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 openWorld, so the safety profile is covered. The description adds genuinely non-inferable behavior: a $0.03 USDC cost, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms without executing. It does not describe result shape, but an output schema exists to carry that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the operation and followed by cost and payment-gating detail. The raw endpoint path is marginally redundant for an agent but is compact and aids traceability; nothing else is wasted.

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?

For a four-parameter read-only analysis tool with full schema coverage, an output schema and rich annotations, the description covers the operation and the unusual payment gate. The only real gap is selection guidance against overlapping level-detection siblings.

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%, so the baseline is 3. The description hints at key semantics ('swing highs and lows' for swingWindow, 'touch counts' for minTouches) but adds no detail on how zoneWidthPct or swingWindow interact, so it does little beyond the schema.

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?

States a specific verb and resource: cluster swing highs and lows from caller-supplied bars into horizontal support/resistance zones with touch counts. That algorithm-level phrasing meaningfully separates it from siblings such as pivot-points or fibonacci-levels, which also produce levels but by different construction.

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 bars' signals the agent must already hold OHLCV data rather than fetching it, and the tool is evidently a level-detection analysis step. There is no explicit statement of when to choose this over pivot-points or fibonacci-levels, and no stated exclusions.

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