Skip to main content
Glama

AINDEX

Candle patterns and market structure

get_patterns
Read-only

Candlestick patterns in the last three candles (engulfing, hammer, shooting star, stars, doji, inside bar and more) and swing structure: higher highs and lows, the bias, and any break of structure or change of character.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueNo
symbolYes
timeframeNo1h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description does add one genuine behavioral fact beyond annotations: the pattern scan is limited to the last three candles, which bounds the lookback window. It omits other useful context, such as whether a venue must be supplied, whether results are computed live or cached, and how sparse data or unsupported symbol/venue combinations are handled.

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?

A single dense sentence that front-loads the pattern catalog and then the structure outputs, with no filler, no restatement of the tool name, and no redundancy. The parenthetical example list earns its place by making the pattern coverage concrete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does a reasonable job of enumerating what comes back (patterns, swing structure, bias, break of structure/change of character), which is the main thing an agent needs. It is incomplete on the input side, though: nothing says which venues actually support pattern detection or what timeframe the 'three candles' refers to when the default is 1h.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description carries the full burden and does not meet it. Symbol (required, with a strict pattern), timeframe (enum with default 1h), and venue (six-value enum spanning crypto venues and equities sources) are never mentioned. The only indirect link is 'last three candles', which hints that timeframe matters, but no default, format, or venue-symbol compatibility is disclosed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete analytical outputs: candlestick pattern detection over the last three candles (engulfing, hammer, shooting star, stars, doji, inside bar) plus swing structure (higher highs/lows, bias, break of structure, change of character). That is far more specific than the title and clearly separates it from raw-candle tools like get_candles. It stops short of a 5 because it never states an operative verb (e.g. 'returns', 'detects') or explicitly contrasts itself with a sibling.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative such as get_candles for raw OHLC data or get_levels for support/resistance. An agent must infer that this tool is the pattern/structure analysis choice purely from the list of outputs. The 'last three candles' phrase implies a short-horizon use case but is not framed as a usage condition.

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