Skip to main content
Glama

get_hip3_instrument

Read-onlyIdempotent

Retrieve mark price, open interest, mid price, and latest timestamp for a specific HIP-3 instrument by providing its case-sensitive symbol.

Instructions

Get details for a single HIP-3 instrument. Symbols are CASE-SENSITIVE (e.g. 'km:US500'). Returns mark price, open interest, mid price, and latest timestamp.

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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResult data object

Implementation Reference

  • src/index.ts:636-641 (registration)
    Registration of 'get_hip3_instruments' tool using registerInstrumentsTool helper. Lists all HIP-3 builder perp instruments.
    // 16. HIP-3 Instruments
    registerInstrumentsTool(
      "get_hip3_instruments",
      "List all available HIP-3 builder perp instruments on Hyperliquid. HIP-3 symbols are CASE-SENSITIVE (e.g. 'km:US500', 'km:TSLA'). Use this to discover valid symbols before querying HIP-3 data.",
      () => api().hyperliquid.hip3.instruments.list()
    );
  • Handler lambda that calls api().hyperliquid.hip3.instruments.list() to fetch all HIP-3 instruments.
    registerInstrumentsTool(
      "get_hip3_instruments",
      "List all available HIP-3 builder perp instruments on Hyperliquid. HIP-3 symbols are CASE-SENSITIVE (e.g. 'km:US500', 'km:TSLA'). Use this to discover valid symbols before querying HIP-3 data.",
      () => api().hyperliquid.hip3.instruments.list()
    );
  • Helper function registerInstrumentsTool which wraps registerTool for instrument-list tools (no input params). It calls the SDK method and formats the response.
    function registerInstrumentsTool(
      name: string,
      description: string,
      sdkCall: () => Promise<unknown[]>
    ): void {
      registerTool(name, description, {}, ListOutputSchema, async () => {
        const data = await sdkCall();
        return formatResponse(data);
      });
    }
  • src/index.ts:643-650 (registration)
    Registration of 'get_hip3_instrument' (singular) tool using registerCurrentTool helper. Gets details for a single HIP-3 instrument.
    // 15b. HIP-3 Single Instrument
    registerCurrentTool(
      "get_hip3_instrument",
      "Get details for a single HIP-3 instrument. Symbols are CASE-SENSITIVE (e.g. 'km:US500'). Returns mark price, open interest, mid price, and latest timestamp.",
      (coin) => api().hyperliquid.hip3.instruments.get(coin),
      Hip3CoinParam,
      normalizeHip3Coin
    );
  • Hip3CoinParam Zod schema describing the case-sensitive HIP-3 coin symbol format, used as input param schema.
    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."
      );
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 minimal behavioral context beyond the listed return fields and case sensitivity.

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, no wasted words. The purpose is front-loaded, and essential details are included without redundancy.

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?

Given the simple one-parameter tool with full schema coverage, annotations, and an output schema (indicated by context), the description covers purpose, case sensitivity, and key return fields, making it 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 coverage is 100%, providing baseline. The description adds value with examples of symbols and a link to the listing tool, which helps the agent understand parameter usage beyond the schema.

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 the verb 'Get', the resource 'details for a single HIP-3 instrument', and distinguishes from siblings like get_hip3_instruments. It also mentions case sensitivity and specific return fields.

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?

The description explicitly notes case sensitivity and provides an alternative 'Use get_hip3_instruments to list all', guiding when to use this tool vs the listing sibling.

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