Skip to main content
Glama

list_transactions

Retrieve transaction history with pagination and currency conversion for crypto wallet operations.

Instructions

List transaction history with cursor-based pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of transactions to return
cursorNoPagination cursor from previous response
display_currencyNoDisplay currency for amount conversion (e.g. KRW, EUR). Defaults to server setting.
wallet_idNoTarget wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.

Implementation Reference

  • The tool registration and implementation for `list_transactions`. It defines the input schema and calls the `apiClient` to fetch transactions.
    export function registerListTransactions(server: McpServer, apiClient: ApiClient, walletContext?: WalletContext): void {
      server.tool(
        'list_transactions',
        withWalletPrefix('List transaction history with cursor-based pagination.', walletContext?.walletName),
        {
          limit: z.number().optional().describe('Maximum number of transactions to return'),
          cursor: z.string().optional().describe('Pagination cursor from previous response'),
          display_currency: z.string().optional().describe('Display currency for amount conversion (e.g. KRW, EUR). Defaults to server setting.'),
          wallet_id: z.string().optional().describe('Target wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.'),
        },
        async (args) => {
          const params = new URLSearchParams();
          if (args.limit !== undefined) params.set('limit', String(args.limit));
          if (args.cursor !== undefined) params.set('cursor', args.cursor);
          if (args.display_currency !== undefined) params.set('display_currency', args.display_currency);
          if (args.wallet_id) params.set('walletId', args.wallet_id);
          const qs = params.toString();
          const result = await apiClient.get(`/v1/transactions${qs ? `?${qs}` : ''}`);
          return toToolResult(result);
        },
      );
    }
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses pagination mechanism (cursor-based) but omits other behavioral traits: read-only nature (implied but not stated), sorting order, transaction filtering logic, or data freshness.

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?

Extremely terse (7 words) and front-loaded with verb. No redundancy, but arguably underspecified given tool complexity (4 parameters, conditional requirements, pagination logic, no output schema).

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

Completeness2/5

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

Insufficient for complexity: 4 parameters with conditional requirements, no output schema, and ambiguous scope relative to siblings (`list_incoming_transactions`). Should clarify transaction scope, output format, or differentiate from similar list operations.

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 has 100% description coverage, establishing baseline 3. Description adds no parameter-specific guidance, examples, or relationships (e.g., that cursor comes from previous response), but schema adequately documents individual fields.

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?

States specific verb (List) and resource (transaction history) and mentions pagination characteristic. However, fails to distinguish from sibling `list_incoming_transactions` or clarify whether this covers all transaction types vs subsets.

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?

Mentions 'cursor-based pagination' which implicitly signals this is for batch retrieval (vs `get_transaction` for single records), but lacks explicit when-to-use guidance, prerequisites, or comparison to `list_incoming_transactions`.

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