Skip to main content
Glama

get_hip3_candles

Read-onlyIdempotent

Fetch OHLCV candle data for HIP-3 instruments. Specify coin symbol, interval (1m to 1w), and time range to get open, high, low, close, volume.

Instructions

Get HIP-3 OHLCV candle data. Symbols are CASE-SENSITIVE (e.g. 'km:US500'). Intervals: 1m to 1w (default 1h). Returns open, high, low, close, volume.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesHIP-3 coin symbol (CASE-SENSITIVE). 125+ markets across 6 builders: xyz, flx, hyna, km, vntl, cash. Examples: 'km:US500', 'xyz:GOLD', 'hyna:BTC', 'vntl:SPACEX', 'flx:TSLA', 'cash:NVDA'. Use get_hip3_instruments to list all.
startNoStart timestamp (Unix ms or ISO). Defaults to 24h ago.
endNoEnd timestamp (Unix ms or ISO). Defaults to now.
limitNoMax records to return (default 100, max 1000)
cursorNoPagination cursor from previous response's nextCursor
intervalNoCandle interval (default '1h')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
recordsYesArray of result records
countYesTotal number of records in the full result set
nextCursorNoCursor for next page, if more results available

Implementation Reference

  • src/index.ts:700-708 (registration)
    Registration of the 'get_hip3_candles' tool via the registerCandleTool helper. The tool is registered with name 'get_hip3_candles', description about HIP-3 OHLCV candle data, and delegates to the SDK method api().hyperliquid.hip3.candles.history(). It uses Hip3CoinParam (CASE-SENSITIVE coin symbols) and normalizeHip3Coin for normalization, with an optional IntervalParam.
    // 19. HIP-3 Candles
    registerCandleTool(
      "get_hip3_candles",
      "Get HIP-3 OHLCV candle data. Symbols are CASE-SENSITIVE (e.g. 'km:US500'). Intervals: 1m to 1w (default 1h). Returns open, high, low, close, volume.",
      (coin, params) =>
        api().hyperliquid.hip3.candles.history(coin, params as any),
      Hip3CoinParam,
      normalizeHip3Coin
    );
  • Hip3CoinParam — the Zod schema for the 'coin' input parameter. Describes HIP-3 coin symbols as CASE-SENSITIVE with examples and references get_hip3_instruments for discovery.
    const Hip3CoinParam = z
      .string()
      .describe(
        "HIP-3 coin symbol (CASE-SENSITIVE). 125+ markets across 6 builders: xyz, flx, hyna, km, vntl, cash. Examples: 'km:US500', 'xyz:GOLD', 'hyna:BTC', 'vntl:SPACEX', 'flx:TSLA', 'cash:NVDA'. Use get_hip3_instruments to list all."
      );
  • IntervalParam — the Zod schema for the optional 'interval' parameter used by the candle tool. Defines valid intervals: 1m, 5m, 15m, 30m, 1h, 4h, 1d, 1w (default 1h).
    const IntervalParam = z
      .enum(["1m", "5m", "15m", "30m", "1h", "4h", "1d", "1w"])
      .optional()
      .describe("Candle interval (default '1h')");
  • registerCandleTool — the helper function that registers candle tools. It calls registerHistoryTool with an extra IntervalParam schema, which in turn calls registerTool to wire up the handler. The handler resolves time range via resolveTimeRange and passes interval through to the SDK.
    function registerCandleTool(
      name: string,
      description: string,
      sdkCall: (coin: string, params: Record<string, unknown>) => Promise<{ data: unknown; nextCursor?: string }>,
      coinSchema: z.ZodString,
      normFn: (coin: string) => string
    ): void {
      registerHistoryTool(
        name,
        description,
        sdkCall,
        coinSchema,
        normFn,
        { interval: IntervalParam }
      );
    }
  • The handler function for get_hip3_candles (inlined in registerCandleTool call). It calls api().hyperliquid.hip3.candles.history(coin, params) where params includes start, end, limit, cursor, and interval. The actual handler logic is contained within the registerCandleTool → registerHistoryTool → registerTool chain.
    // 19. HIP-3 Candles
    registerCandleTool(
      "get_hip3_candles",
      "Get HIP-3 OHLCV candle data. Symbols are CASE-SENSITIVE (e.g. 'km:US500'). Intervals: 1m to 1w (default 1h). Returns open, high, low, close, volume.",
      (coin, params) =>
        api().hyperliquid.hip3.candles.history(coin, params as any),
      Hip3CoinParam,
      normalizeHip3Coin
    );
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that it returns OHLCV data and interval details but does not disclose behavioral traits like pagination behavior or rate limits beyond what annotations provide.

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?

The description is three concise sentences front-loaded with the main purpose, followed by key details (case-sensitivity and intervals). Every sentence earns its place with no wasted words.

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?

Given the output schema exists, the description appropriately omits return value details but covers purpose, symbol format, and intervals. It does not mention pagination (cursor parameter), but the schema handles that. Overall fairly complete for a simple data tool.

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?

Input schema has 100% description coverage, so the baseline is 3. The description reinforces case-sensitivity and intervals but does not add significant meaning beyond the schema's parameter descriptions.

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 clearly states 'Get HIP-3 OHLCV candle data', specifying the exact resource (HIP-3 candles) and differentiating from sibling tools like get_candles (non-HIP-3) and other get_hip3_* tools for different data types.

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

Usage Guidelines4/5

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

It provides clear usage context (case-sensitive symbols, intervals) but does not explicitly mention when to use this tool vs alternatives like get_candles or other candle tools. This is a minor gap for an otherwise clear purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/0xArchiveIO/0xarchive-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server