Skip to main content
Glama

get_hip4_trades_recent

Read-onlyIdempotent

Retrieve the most recent HIP-4 trades for a specific coin by providing its symbol, without requiring a time range.

Instructions

Get the most recent HIP-4 trades for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns the latest trades without needing a time range.

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.
limitNoMax records to return (default 100, max 1000)

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:1675-1693 (registration)
    Registration of the 'get_hip4_trades_recent' tool. It defines input schema (coin + optional limit), uses ListOutputSchema, and calls the REST API at `/trades/{coin}/recent`.
    // HIP-4 Recent Trades
    registerTool(
      "get_hip4_trades_recent",
      "Get the most recent HIP-4 trades for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns the latest trades without needing a time range.",
      {
        coin: Hip4CoinParam,
        limit: LimitParam,
      },
      ListOutputSchema,
      async (params) => {
        const q: Record<string, unknown> = {};
        if (params.limit) q.limit = resolveLimit(params.limit);
        const result = await hip4Request(
          `/trades/${normalizeHip4Coin(params.coin)}/recent`,
          q
        );
        return formatResponse(result.data);
      }
    );
  • Handler function for get_hip4_trades_recent. Builds a query object with an optional limit, calls hip4Request to GET `/trades/{normalizedCoin}/recent`, and returns the response data.
    async (params) => {
      const q: Record<string, unknown> = {};
      if (params.limit) q.limit = resolveLimit(params.limit);
      const result = await hip4Request(
        `/trades/${normalizeHip4Coin(params.coin)}/recent`,
        q
      );
      return formatResponse(result.data);
    }
  • Input schema for get_hip4_trades_recent: coin (HIP-4 coin symbol) and optional limit. Output schema is ListOutputSchema (records, count, nextCursor).
    {
      coin: Hip4CoinParam,
      limit: LimitParam,
    },
    ListOutputSchema,
  • Helper function hip4Request that sends GET requests to the HIP-4 REST API path. Used by get_hip4_trades_recent to call `/trades/{coin}/recent`.
    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);
      }
    }
  • Normalization helper for HIP-4 coin symbols. Strips legacy '#' / '%23' prefixes to canonical bare numeric form.
    function normalizeHip4Coin(coin: string): string {
      const trimmed = String(coin).trim();
      if (/^\d+$/.test(trimmed)) return trimmed;
      const stripped = trimmed.replace(/^(#|%23)/i, "");
      if (/^\d+$/.test(stripped)) return stripped;
      // Unknown shape — fall back to URL-encoding the original.
      return encodeURIComponent(trimmed);
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds minimal behavioral context (latest trades) but does not disclose any additional traits 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 two sentences, front-loaded with the primary action, and every sentence adds useful information 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 presence of an output schema and detailed annotations, the description sufficiently covers the tool's purpose and coin parameter, making it complete for a simple recent-trades retrieval tool.

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%. The description adds value by explaining the coin format with examples and legacy forms, which enhances meaning beyond the schema's descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves the most recent HIP-4 trades for a coin, with an example. It distinguishes itself from time-range-based queries by noting 'without needing a time range', but does not explicitly differentiate from sibling tools like get_hip4_trades.

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 indicates when to use (to get latest trades without a time range) but does not provide explicit guidance on when not to use or alternatives like get_hip4_trades for historical data.

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