Skip to main content
Glama

get_hip3_l2_diffs

Read-onlyIdempotent

Retrieve HIP-3 L2 orderbook diffs showing price-level changes for case-sensitive coin symbols across 6 builders. Supports time range filters and pagination.

Instructions

Get HIP-3 L2 tick-level orderbook diffs (Pro+ tier). Symbols are CASE-SENSITIVE. Returns price-level changes.

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

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:1297-1305 (registration)
    Registration of the 'get_hip3_l2_diffs' tool using registerHistoryTool helper. It accepts a HIP-3 coin symbol (case-sensitive), time range params (start, end, limit, cursor), and calls api().hyperliquid.hip3.l2Orderbook.diffs(coin, params).
    // HIP-3 L2 Diffs
    registerHistoryTool(
      "get_hip3_l2_diffs",
      "Get HIP-3 L2 tick-level orderbook diffs (Pro+ tier). Symbols are CASE-SENSITIVE. Returns price-level changes.",
      (coin, params) =>
        api().hyperliquid.hip3.l2Orderbook.diffs(coin, params as any),
      Hip3CoinParam,
      normalizeHip3Coin
    );
  • The handler for 'get_hip3_l2_diffs' is an inline arrow function that takes (coin, params) and returns api().hyperliquid.hip3.l2Orderbook.diffs(coin, params as any). It is wrapped by the registerHistoryTool pattern which handles time range resolution, pagination via cursor, and formatting.
    registerHistoryTool(
      "get_hip3_l2_diffs",
      "Get HIP-3 L2 tick-level orderbook diffs (Pro+ tier). Symbols are CASE-SENSITIVE. Returns price-level changes.",
      (coin, params) =>
        api().hyperliquid.hip3.l2Orderbook.diffs(coin, params as any),
      Hip3CoinParam,
      normalizeHip3Coin
    );
  • The Hip3CoinParam Zod schema used as the coin parameter input schema for the HIP-3 tool. It describes the case-sensitive coin symbols (e.g. 'km:US500', 'xyz:GOLD').
    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."
      );
  • The ListOutputSchema Zod schema used as the output schema for the tool. Defines the shape of responses: records array, count number, and optional nextCursor.
    const ListOutputSchema: ZodRawShape = {
      records: z.array(z.record(z.unknown())).describe("Array of result records"),
      count: z.number().describe("Total number of records in the full result set"),
      nextCursor: z
        .string()
        .optional()
        .describe("Cursor for next page, if more results available"),
    };
  • The registerHistoryTool helper function that wires up the tool registration. It handles time range resolution (resolveTimeRange), limit defaults, cursor passthrough, and formats responses via formatCursorResponse. This is the pattern used to register get_hip3_l2_diffs.
    function registerHistoryTool(
      name: string,
      description: string,
      sdkCall: (coin: string, params: Record<string, unknown>) => Promise<{ data: unknown; nextCursor?: string }>,
      coinSchema: z.ZodString,
      normFn: (coin: string) => string,
      extraSchema?: ZodRawShape
    ): void {
      const schema: ZodRawShape = { coin: coinSchema, ...HistoryParams };
      if (extraSchema) Object.assign(schema, extraSchema);
    
      registerTool(name, description, schema, ListOutputSchema, async (params) => {
        const { coin, start, end, limit, cursor, ...extra } = params;
    
        const timeRange = resolveTimeRange(start, end);
        const sdkParams: Record<string, unknown> = {
          ...timeRange,
          limit: resolveLimit(limit),
        };
    
        if (cursor) sdkParams.cursor = cursor;
    
        // Pass through extra params (interval, side, etc.)
        for (const [k, v] of Object.entries(extra)) {
          if (v !== undefined) sdkParams[k] = v;
        }
    
        const result = await sdkCall(normFn(coin), sdkParams);
        return formatCursorResponse(result);
      });
    }
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds value by stating 'Returns price-level changes' and 'tick-level orderbook diffs', clarifying the output behavior beyond annotations.

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?

Two sentences, front-loaded with purpose and tier. No redundancy. Every sentence contributes meaningful information.

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 output schema exists, description doesn't need to detail return format. It adequately conveys that diffs are price-level changes. Missing explicit mention of pagination, but schema covers cursor. Overall complete.

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

Parameters4/5

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

Schema has 100% description coverage. Description reinforces case-sensitivity and adds market context (125+ markets, 6 builders, examples). This adds value beyond the schema 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?

Description clearly states verb 'Get', resource 'HIP-3 L2 tick-level orderbook diffs', and notes Pro+ tier. It distinguishes from siblings like get_hip3_l2_orderbook by specifying 'diffs' and 'price-level changes'.

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?

Implied usage via 'Pro+ tier' and 'tick-level orderbook diffs', but no explicit when-to-use or when-not-to-use compared to alternatives like get_hip3_l2_orderbook. The coin parameter references get_hip3_instruments for listing symbols, which aids usage but is not a direct guideline.

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