Skip to main content
Glama

Price candles

get_price_candles
Read-onlyIdempotent

Price history for one coin as candles: open, high, low, close and volume per interval (1m, 5m, 15m, 1h, 4h, 1d), up to 500, oldest first, from Hyperliquid's public market, the same prices the sandbox trades at. Use to look back at price action, find recent highs and lows for a stop, or judge the trend. Not for the live best price (use compare_venue_prices) or ready-made indicators (use get_technical_indicators). Inputs: symbol (base coin), interval (default 1h), limit (default 100). Prices in USD per coin, volume in the base coin, times UTC. Next: size_position.

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_price_candles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many candles, newest last (1-500)
symbolYesBase coin, e.g. BTC
intervalNoCandle length1h

Output Schema

NameRequiredDescriptionDefault
lowYesLowest low over these candles, USD per coin
highYesHighest high over these candles, USD per coin
sourceYesWhere the prices come from
symbolYesBase coin
candlesYesOldest first
intervalYesCandle length
change_pctYesFrom the first open to the last close, as a fraction
deprecationNoPresent only while this tool is deprecated: replacement, removal_date, changelog

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed31 schema fields changed
    • removedInput schema / properties / interval / title
      Removed value: -"Interval"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedInput schema / title
      Removed value: -"get_price_candlesArguments"
    • removedOutput schema / $defs / Candle / properties / close / title
      Removed value: -"Close"
    • addedOutput schema / $defs / Candle / properties / deprecation / additionalProperties
      Added value: +true
    • removedOutput schema / $defs / Candle / properties / deprecation / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / $defs / Candle / properties / deprecation / default
      Removed value: -null
    • removedOutput schema / $defs / Candle / properties / deprecation / title
      Removed value: -"Deprecation"
    • addedOutput schema / $defs / Candle / properties / deprecation / type
      Added value: +[
      +  "object",
      +  "null"
      +]
    • removedOutput schema / $defs / Candle / properties / high / title
      Removed value: -"High"
    • removedOutput schema / $defs / Candle / properties / low / title
      Removed value: -"Low"
    • removedOutput schema / $defs / Candle / properties / open / title
      Removed value: -"Open"
    • removedOutput schema / $defs / Candle / properties / time / title
      Removed value: -"Time"
    • removedOutput schema / $defs / Candle / properties / volume / title
      Removed value: -"Volume"
    • removedOutput schema / $defs / Candle / title
      Removed value: -"Candle"
    • removedOutput schema / properties / candles / title
      Removed value: -"Candles"
    • removedOutput schema / properties / change_pct / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / change_pct / title
      Removed value: -"Change Pct"
    • addedOutput schema / properties / change_pct / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • addedOutput schema / properties / deprecation / additionalProperties
      Added value: +true
    • removedOutput schema / properties / deprecation / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / deprecation / default
      Removed value: -null
    • removedOutput schema / properties / deprecation / title
      Removed value: -"Deprecation"
    • addedOutput schema / properties / deprecation / type
      Added value: +[
      +  "object",
      +  "null"
      +]
    • removedOutput schema / properties / high / title
      Removed value: -"High"
    • removedOutput schema / properties / interval / title
      Removed value: -"Interval"
    • removedOutput schema / properties / low / title
      Removed value: -"Low"
    • removedOutput schema / properties / source / title
      Removed value: -"Source"
    • removedOutput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedOutput schema / title
      Removed value: -"Candles"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so safety is covered; the description goes further by disclosing data provenance ('Hyperliquid's public market, the same prices the sandbox trades at'), the 500-candle cap, oldest-first ordering, and units (USD per coin, volume in base coin, UTC times). These are behavioral facts an agent cannot obtain from the annotations and would otherwise have to guess.

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?

Front-loaded with the core purpose, then usage, then exclusions, then inputs — a sensible progression where nearly every clause carries information. The 'Inputs:' recital partly duplicates the schema and the 'Next: size_position' nudge is optional, keeping it just short of maximal efficiency.

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

Completeness5/5

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

For a three-parameter read tool with a full input schema and an output schema, the description supplies everything else that matters: data source, ordering, cap, units, and timezone. Nothing needed to call or interpret the call correctly is left unstated.

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 schema already documents symbol, interval, and limit with defaults and bounds; the description's 'Inputs:' line largely restates them. It adds only marginal meaning (e.g. 'symbol (base coin)' and reinforcing the default interval/limit) rather than new constraints or semantics.

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 ('Price history for one coin as candles') and enumerates the returned fields (open, high, low, close, volume per interval), so an agent immediately knows this is OHLCV retrieval rather than a quote or indicator endpoint. It is clearly separable from siblings like get_order_book, get_technical_indicators, and compare_venue_prices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives positive use cases (look back at price action, find recent highs/lows for a stop, judge the trend) and explicit exclusions with named alternatives: 'Not for the live best price (use compare_venue_prices) or ready-made indicators (use get_technical_indicators).' It also signals the follow-on step ('Next: size_position'), leaving little to inference.

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