Skip to main content
Glama

Candles with footprint

candles
Read-only

OHLC candles with aggressive buy and sell volume, delta and point of control (POC). With footprint=true, each candle also has its price levels with bought and sold volume (at most 20 candles).

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": {
      "pair": "<pair>"
    },
    "name": "candles"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR
limitNoNumber of most recent candles (1 to 200)
footprintNoInclude the price levels of each candle with bought and sold volume (max 20 candles)
timeframeNoCandle timeframe: 1m, 5m, 15m, 1h, 4h, 1d or 1w1h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context in the 20-candle cap when footprint is enabled, but it says nothing about rate limits, ordering, or what happens when limit exceeds the footprint cap.

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?

Two compact sentences, front-loaded with what the tool returns before the conditional footprint behavior. The second sentence duplicates schema wording, which is mild redundancy but also the most decision-relevant detail.

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 no output schema, the description must convey return shape, and it does: OHLC fields plus volume, delta, POC, and optional per-level data. Gaps remain around ordering and the interaction between limit and the 20-candle footprint ceiling, but nothing essential for calling the tool is missing.

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 pair, limit, timeframe, and footprint are all documented in the schema itself. The description's footprint clause largely restates the schema text (price levels with bought and sold volume, max 20 candles) and adds no format or interaction detail beyond it, matching the baseline of 3.

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 specific resource (OHLC candles) and enumerates the payload fields: aggressive buy/sell volume, delta, and point of control. That is far more specific than the title 'Candles with footprint', but it never contrasts itself with siblings such as cvd or market_snapshot, so an agent must infer the boundary.

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?

There is no explicit when-to-use or when-not-to-use guidance versus the sibling tools. The only usage signal is conditional: set footprint=true when per-price-level volume is needed, which is implied rather than stated as guidance.

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