Skip to main content
Glama

get_hip3_instruments

Read-onlyIdempotent

Retrieve the list of all available HIP-3 builder perpetual instruments on Hyperliquid. Use this tool to discover valid case-sensitive symbols before querying HIP-3 data.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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:636-641 (registration)
    Registration of the 'get_hip3_instruments' tool using the registerInstrumentsTool helper. It delegates to api().hyperliquid.hip3.instruments.list().
    // 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 helper: registerInstrumentsTool wraps the SDK call and formats the response. This is the actual handler invoked when the tool runs.
    function registerInstrumentsTool(
      name: string,
      description: string,
      sdkCall: () => Promise<unknown[]>
    ): void {
      registerTool(name, description, {}, ListOutputSchema, async () => {
        const data = await sdkCall();
        return formatResponse(data);
      });
  • Output schema (ListOutputSchema) used by get_hip3_instruments. Defines the shape: records array, count, 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"),
    };
  • Core registration helper: registerTool wraps server.registerTool with API key guard and error handling. Used by registerInstrumentsTool (which registers get_hip3_instruments).
    function registerTool(
      name: string,
      description: string,
      inputSchema: ZodRawShape,
      outputSchema: ZodRawShape,
      handler: (params: any) => Promise<McpContent>
    ): void {
      server.registerTool(
        name,
        {
          description,
          inputSchema,
          outputSchema,
          annotations: TOOL_ANNOTATIONS,
        },
        async (params: any) => {
          if (!client) {
            return {
              content: [{ type: "text" as const, text: MISSING_KEY_MESSAGE }],
              isError: true,
            };
          }
          try {
            return await handler(params);
          } catch (err) {
            const error = err instanceof OxArchiveError ? err : new OxArchiveError(String(err), 500);
            return formatError(error);
          }
        }
      );
    }
    
    // Pattern 1: Instrument list (no params)
    function registerInstrumentsTool(
      name: string,
      description: string,
      sdkCall: () => Promise<unknown[]>
    ): void {
      registerTool(name, description, {}, ListOutputSchema, async () => {
        const data = await sdkCall();
        return formatResponse(data);
      });
    }
Behavior4/5

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

Annotations already declare readOnlyHint true and idempotentHint true; description adds important behavioral detail about case-sensitivity. No contradictions.

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 efficient sentences: one for purpose, one for critical usage note. No wasted words.

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 no parameters and existing output schema and annotations, the description provides sufficient context about what the tool returns and how to use it.

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?

No parameters exist, so schema coverage is 100%. Description adds meaning by explaining the output context (list of HIP-3 instruments) 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 it lists all available HIP-3 builder perp instruments and distinguishes from siblings by specifying HIP-3 context. It also notes case-sensitivity, which is a key detail.

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?

The description explicitly guides to use this tool to discover valid symbols before querying other HIP-3 data, but does not mention when not to use or compare to similar tools like get_hip3_instrument.

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