Skip to main content
Glama

list_offchain_actions

Retrieve and filter signed off-chain transaction history by venue and status with pagination controls for wallet management.

Instructions

List off-chain action history (signedData/signedHttp) with venue/status filter and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
venueNoFilter by venue name (e.g. polymarket, hyperliquid)
statusNoFilter by status (e.g. PENDING, FILLED, CANCELED, EXPIRED)
limitNoMaximum number of results to return
offsetNoPagination offset
wallet_idNoWallet ID. Auto-resolved for single-wallet sessions.

Implementation Reference

  • The handler function that executes the logic to list offchain actions by calling the API.
    async (args) => {
      const walletId = args.wallet_id || 'default';
      const params = new URLSearchParams();
      if (args.venue !== undefined) params.set('venue', args.venue);
      if (args.status !== undefined) params.set('status', args.status);
      if (args.limit !== undefined) params.set('limit', String(args.limit));
      if (args.offset !== undefined) params.set('offset', String(args.offset));
      const qs = params.toString();
      const result = await apiClient.get(`/v1/wallets/${walletId}/actions${qs ? `?${qs}` : ''}`);
      return toToolResult(result);
    },
  • The Zod schema validation for the list_offchain_actions tool.
    {
      venue: z.string().optional().describe('Filter by venue name (e.g. polymarket, hyperliquid)'),
      status: z.string().optional().describe('Filter by status (e.g. PENDING, FILLED, CANCELED, EXPIRED)'),
      limit: z.number().optional().describe('Maximum number of results to return'),
      offset: z.number().optional().describe('Pagination offset'),
      wallet_id: z.string().optional().describe('Wallet ID. Auto-resolved for single-wallet sessions.'),
    },
  • The registration function for the list_offchain_actions tool.
    export function registerListOffchainActions(
      server: McpServer,
      apiClient: ApiClient,
      walletContext?: WalletContext,
    ): void {
      server.tool(
        'list_offchain_actions',
        withWalletPrefix(
          'List off-chain action history (signedData/signedHttp) with venue/status filter and pagination.',
          walletContext?.walletName,
        ),
        {
          venue: z.string().optional().describe('Filter by venue name (e.g. polymarket, hyperliquid)'),
          status: z.string().optional().describe('Filter by status (e.g. PENDING, FILLED, CANCELED, EXPIRED)'),
          limit: z.number().optional().describe('Maximum number of results to return'),
          offset: z.number().optional().describe('Pagination offset'),
          wallet_id: z.string().optional().describe('Wallet ID. Auto-resolved for single-wallet sessions.'),
        },
        async (args) => {
          const walletId = args.wallet_id || 'default';
          const params = new URLSearchParams();
          if (args.venue !== undefined) params.set('venue', args.venue);
          if (args.status !== undefined) params.set('status', args.status);
          if (args.limit !== undefined) params.set('limit', String(args.limit));
          if (args.offset !== undefined) params.set('offset', String(args.offset));
          const qs = params.toString();
          const result = await apiClient.get(`/v1/wallets/${walletId}/actions${qs ? `?${qs}` : ''}`);
          return toToolResult(result);
        },
      );
    }
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It mentions pagination (suggesting large datasets) and filters, but omits critical behavioral details like default ordering (newest first?), return format structure, or explicit confirmation that this is read-only despite the 'List' verb implying safety.

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 a single, front-loaded sentence of 16 words with zero redundancy. Every element earns its place: the verb and resource are immediate, parenthetical examples clarify the abstract 'off-chain actions,' and the capability clause summarizes filtering/pagination without repeating parameter details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 100% schema coverage and straightforward filter-and-paginate pattern, the description adequately covers the tool's purpose. However, lacking an output schema, it should ideally describe the return structure (e.g., 'returns array of action records') to be complete for an agent selecting tools.

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?

Input schema has 100% description coverage with clear explanations for all five parameters including helpful examples (polymarket, hyperliquid) and auto-resolution notes for wallet_id. The description mentions filter categories but adds no semantic meaning beyond what the schema already provides, warranting the baseline score.

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 identifies the resource (off-chain action history) and specifies the action types (signedData/signedHttp), which distinguishes it from on-chain transaction siblings like list_transactions. The verb 'List' is specific and the scope is well-defined with parenthetical examples.

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 mentions available filters (venue/status) and pagination, implying when to use the tool for filtered history retrieval. However, it lacks explicit guidance on when NOT to use it or how to choose between this general listing tool and venue-specific siblings like waiaas_hl_get_trade_history.

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/minhoyoo-iotrust/WAIaaS'

If you have feedback or need assistance with the MCP directory API, please join our Discord server