Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Detect chart patterns from swing points

technical-analysis_chart-patterns
Read-onlyIdempotent

Find swing highs and lows, then detect double tops and bottoms, head and shoulders (and inverse), triangles and rectangles with necklines, targets and confirmation. Price $0.05 USDC. POST /api/v1/technical-analysis/chart-patterns. 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_chart-patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
toleranceNotolerance, number, from any to 1. Required.
swingWindowNoswingWindow, integer, from 1 to 500. Required.
minBarsBetweenNominBarsBetween, integer, from 1 to 5000. Required.

Output Schema

NameRequiredDescriptionDefault
paramsNoparams. Object.
swingsNoswings. Array.
warmupNowarmup. Object.
sourcesNosources. Array.
patternsNopatterns. 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 cover read-only, idempotent and non-destructive safety, and the description goes meaningfully beyond them by disclosing cost ($0.05 USDC), the x402 payment flow, and the critical behavior that an unpaid call returns payment terms instead of results. It stops short of stating limits on bar count, rate behavior, or how many patterns are returned, which keeps it from a 5.

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: capability first, commercial/payment terms after. Each element carries operational weight, though the raw endpoint path duplicates what a transport layer typically supplies and adds little for the agent.

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 covering return values and annotations covering safety, the description supplies the one thing an agent could not otherwise know: that the call is paid and how an unpaid call behaves. It lacks guidance on input data prerequisites (minimum bar count, bar interval) for a pattern detector that is sensitive to those, so not quite complete.

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 baseline is 3. The description gestures at swing-point logic but adds no meaning for tolerance, swingWindow or minBarsBetween beyond the schema, whose descriptions are largely generic type restatements; it never explains how tolerance affects pattern matching or how swingWindow trades off sensitivity.

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 chain (find swing highs/lows, then detect) and enumerates the exact pattern set returned: double tops/bottoms, head and shoulders and inverse, triangles, rectangles, with necklines, targets and confirmation. That enumeration distinguishes it cleanly from candlestick-patterns, pivot-points and support-resistance siblings 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?

The description implies the use case (detect geometric chart patterns over OHLCV bars) and states the payment prerequisite, but never says when to prefer this over pivot-points or candlestick-patterns, nor any exclusions such as needing a minimum history length. Usage is inferable rather than prescribed.

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