Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Detect candlestick patterns

technical-analysis_candlestick-patterns
Read-onlyIdempotent

Detect doji, hammer, shooting star, engulfing, harami, piercing line, dark cloud cover, morning/evening star, three white soldiers, three black crows and marubozu using explicit numeric thresholds you can override. Price $0.04 USDC. POST /api/v1/technical-analysis/candlestick-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_candlestick-patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
patternsNopatterns, array. Required.
thresholdsNothresholds, object. Required.
trendLookbackNotrendLookback, integer, from 2 to 1000. Required.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the description correctly spends its words elsewhere: it discloses the $0.04 USDC cost and, importantly, that an unpaid call returns x402 payment terms and does not execute — a critical gating behavior an agent must know. It does not disclose minimum bar counts or failure conditions for insufficient data.

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 capability, followed by the override note and the payment/transport facts. The endpoint URL is mildly redundant with the tool name but still useful for direct calls; 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?

An output schema exists, so return values need not be explained, and the payment gating plus endpoint are covered. Given a nested bars array and a trendLookback parameter whose role is non-obvious, the definition could say more about input requirements, but the essentials for calling are present.

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 schema already documents all four parameters and their defaults. The description adds only that thresholds are 'explicit numeric thresholds you can override'; it does not clarify what trendLookback controls (trend context for star patterns) or the required OHLCV bar shape, which is the tool's most consequential input constraint.

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 ('Detect') and resource ('candlestick patterns'), then enumerates the exact pattern set (doji, hammer, engulfing, harami, morning/evening star, marubozu, etc.), which clearly separates it from the sibling chart-patterns tool without the agent needing to open either 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 never says when to reach for this tool versus technical-analysis_chart-patterns or the other indicator siblings, nor what input preconditions matter (e.g., how many bars are needed for multi-bar patterns). Only the threshold-override hint implies any usage context.

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