Skip to main content
Glama

get_hip4_tpsl

Read-onlyIdempotent

Retrieve take-profit and stop-loss order history for a HIP-4 outcome market coin, including trigger prices and triggered status.

Instructions

Get HIP-4 TP/SL order history (Pro+ tier) for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns take-profit and stop-loss orders with trigger prices and triggered status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesHIP-4 outcome-market coin symbol. Canonical form is the bare numeric '<10*outcome_id + side>' (e.g. '0' for outcome 0 Yes, '1' for outcome 0 No, '10' for outcome 1 Yes). The legacy '#0' and '%230' forms are also accepted. Use get_hip4_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
userNoUser wallet address filter (e.g., '0x1234...')
triggeredNoFilter TP/SL orders by triggered status

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:1828-1850 (registration)
    Registration of the 'get_hip4_tpsl' tool via registerTool (which calls server.registerTool under the hood). Defines input schema (coin, history params, user, triggered) and the inline async handler.
    // HIP-4 TP/SL
    registerTool(
      "get_hip4_tpsl",
      "Get HIP-4 TP/SL order history (Pro+ tier) for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns take-profit and stop-loss orders with trigger prices and triggered status.",
      {
        coin: Hip4CoinParam,
        ...HistoryParams,
        user: UserParam,
        triggered: TriggeredParam,
      },
      ListOutputSchema,
      async (params) => {
        const q = buildHistoryQuery(params.start, params.end, params.limit, params.cursor, {
          user: params.user,
          triggered: params.triggered,
        });
        const result = await hip4Request(
          `/orders/${normalizeHip4Coin(params.coin)}/tpsl`,
          q
        );
        return formatCursorResponse(result);
      }
    );
  • The inline handler function for get_hip4_tpsl. Builds a query object from params, calls hip4Request to GET /v1/hyperliquid/hip4/orders/<coin>/tpsl, and formats the cursor-paginated response.
    async (params) => {
      const q = buildHistoryQuery(params.start, params.end, params.limit, params.cursor, {
        user: params.user,
        triggered: params.triggered,
      });
      const result = await hip4Request(
        `/orders/${normalizeHip4Coin(params.coin)}/tpsl`,
        q
      );
      return formatCursorResponse(result);
    }
  • Helper function used by get_hip4_tpsl to build a query object with start/end timestamps, limit, cursor, and any extra params (user, triggered).
    function buildHistoryQuery(
      start?: number | string,
      end?: number | string,
      limit?: number,
      cursor?: string,
      extra?: Record<string, unknown>
    ): Record<string, unknown> {
      const range = resolveTimeRange(start, end);
      const q: Record<string, unknown> = {
        start: range.start,
        end: range.end,
        limit: resolveLimit(limit),
      };
      if (cursor) q.cursor = cursor;
      if (extra) {
        for (const [k, v] of Object.entries(extra)) {
          if (v !== undefined) q[k] = v;
        }
      }
      return q;
    }
  • Generic REST helper used by get_hip4_tpsl (and all HIP-4 tools) to make authenticated GET requests to the 0xArchive API with query parameters, error handling, and cursor extraction.
    async function hip4Request(
      path: string,
      query?: Record<string, unknown>
    ): Promise<{ data: unknown; nextCursor?: string }> {
      const url = new URL(`${HIP4_BASE_PATH}${path}`, HIP4_BASE_URL);
      if (query) {
        for (const [k, v] of Object.entries(query)) {
          if (v === undefined || v === null) continue;
          url.searchParams.set(k, String(v));
        }
      }
      const headers: Record<string, string> = {
        "Content-Type": "application/json",
        "User-Agent": "0xarchive-mcp/1.9.0",
      };
      if (apiKey) headers["X-API-Key"] = apiKey;
    
      const controller = new AbortController();
      const timeout = setTimeout(() => controller.abort(), 60000);
      try {
        const response = await fetch(url.toString(), {
          method: "GET",
          headers,
          signal: controller.signal,
        });
        const text = await response.text();
        let body: any;
        try {
          body = text ? JSON.parse(text) : null;
        } catch {
          body = text;
        }
        if (!response.ok) {
          const requestId =
            response.headers.get("x-request-id") || body?.meta?.requestId;
          const message =
            (body && (body.error?.message || body.error || body.message)) ||
            `HTTP ${response.status}`;
          throw new OxArchiveError(message, response.status, requestId ?? undefined);
        }
        if (body && typeof body === "object" && "data" in body) {
          return {
            data: body.data,
            nextCursor: body.meta?.nextCursor,
          };
        }
        return { data: body };
      } finally {
        clearTimeout(timeout);
      }
    }
  • Input schema for the 'coin' parameter used by get_hip4_tpsl — validates HIP-4 coin symbols.
    const Hip4CoinParam = z
      .string()
      .describe(
        "HIP-4 outcome-market coin symbol. Canonical form is the bare numeric '<10*outcome_id + side>' (e.g. '0' for outcome 0 Yes, '1' for outcome 0 No, '10' for outcome 1 Yes). The legacy '#0' and '%230' forms are also accepted. Use get_hip4_instruments to list all."
      );
  • Output schema used by get_hip4_tpsl — defines the list response shape with records, 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"),
    };
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds value beyond this by specifying that it returns take-profit and stop-loss orders with trigger prices and triggered status, and that it accepts legacy coin forms. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main purpose and is brief (two sentences). It efficiently conveys the core functionality without unnecessary verbosity, though it could be slightly more structured for readability.

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 presence of an output schema, the description does not need to detail return values. It covers input coin format, output content (TP/SL orders with trigger prices and status), and mentions pagination only implicitly via the cursor parameter in schema. The description is adequate for this type of read-history 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?

Schema description coverage is 100%, so baseline is 3. The description adds minor semantic value by clarifying that 'bare numeric coins are canonical' and legacy forms are accepted, but does not elaborate on other parameters beyond what the schema provides.

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 action ('Get'), resource ('HIP-4 TP/SL order history'), and tier ('Pro+ tier'), distinguishing it from sibling tools like get_hip3_tpsl or get_tpsl. The example '0' helps immediately identify the coin format.

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?

The description implies usage for HIP-4 Pro+ tiers via the name and tier mention, but it does not explicitly state when to use this vs alternatives (e.g., for legacy HIP-3 or non-tiered TP/SL). No 'when not to use' or direct sibling comparison.

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