Skip to main content
Glama

list_incoming_transactions

Retrieve received transaction history with pagination and filtering options for monitoring wallet activity across supported chains.

Instructions

List incoming (received) transaction history with cursor-based pagination. Returns confirmed incoming transfers by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of transactions to return (1-100, default 20)
cursorNoPagination cursor from previous response
chainNoFilter by chain (solana or ethereum)
networkNoFilter by network (e.g., "polygon-mainnet" or CAIP-2 "eip155:137").
statusNoFilter by status: DETECTED or CONFIRMED (default: CONFIRMED)
tokenNoFilter by token address (null for native transfers)
from_addressNoFilter by sender address
sinceNoFilter: only transactions detected after this epoch (seconds)
untilNoFilter: only transactions detected before this epoch (seconds)
wallet_idNoTarget wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.

Implementation Reference

  • The handler function for list_incoming_transactions which processes the tool arguments and makes the API call to the backend.
      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.chain !== undefined) params.set('chain', args.chain);
        if (args.network !== undefined) params.set('network', args.network);
        if (args.status !== undefined) params.set('status', args.status);
        if (args.token !== undefined) params.set('token', args.token);
        if (args.from_address !== undefined) params.set('from_address', args.from_address);
        if (args.since !== undefined) params.set('since', String(args.since));
        if (args.until !== undefined) params.set('until', String(args.until));
        if (args.wallet_id) params.set('wallet_id', args.wallet_id);
        const qs = params.toString();
        const result = await apiClient.get(`/v1/wallet/incoming${qs ? `?${qs}` : ''}`);
        return toToolResult(result);
      },
    );
  • The registration function that registers the 'list_incoming_transactions' tool with the MCP server and defines its input schema.
    export function registerListIncomingTransactions(
      server: McpServer,
      apiClient: ApiClient,
      walletContext?: WalletContext,
    ): void {
      server.tool(
        'list_incoming_transactions',
        withWalletPrefix(
          'List incoming (received) transaction history with cursor-based pagination. Returns confirmed incoming transfers by default.',
          walletContext?.walletName,
        ),
        {
          limit: z.number().optional().describe('Maximum number of transactions to return (1-100, default 20)'),
          cursor: z.string().optional().describe('Pagination cursor from previous response'),
          chain: z.string().optional().describe('Filter by chain (solana or ethereum)'),
          network: z.string().optional().describe('Filter by network (e.g., "polygon-mainnet" or CAIP-2 "eip155:137").'),
          status: z.string().optional().describe('Filter by status: DETECTED or CONFIRMED (default: CONFIRMED)'),
          token: z.string().optional().describe('Filter by token address (null for native transfers)'),
          from_address: z.string().optional().describe('Filter by sender address'),
          since: z.number().optional().describe('Filter: only transactions detected after this epoch (seconds)'),
          until: z.number().optional().describe('Filter: only transactions detected before this epoch (seconds)'),
          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.chain !== undefined) params.set('chain', args.chain);
          if (args.network !== undefined) params.set('network', args.network);
          if (args.status !== undefined) params.set('status', args.status);
          if (args.token !== undefined) params.set('token', args.token);
          if (args.from_address !== undefined) params.set('from_address', args.from_address);
          if (args.since !== undefined) params.set('since', String(args.since));
          if (args.until !== undefined) params.set('until', String(args.until));
          if (args.wallet_id) params.set('wallet_id', args.wallet_id);
          const qs = params.toString();
          const result = await apiClient.get(`/v1/wallet/incoming${qs ? `?${qs}` : ''}`);
          return toToolResult(result);
        },
      );
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the pagination mechanism ('cursor-based') and default status filter ('CONFIRMED'), but omits other behavioral traits like rate limits, authentication requirements, or whether the operation is read-only (though implied by 'List').

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 sentences efficiently front-load critical information: the first covers purpose and pagination method, the second covers default filtering behavior. No waste or redundant information.

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?

With 10 well-documented parameters and no output schema, the description adequately covers the operation's intent but lacks detail on return structure or response format that would help the agent understand what data structure to expect.

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%, establishing a baseline of 3. The description adds minimal semantic value beyond the schema, though it contextualizes the cursor parameter by mentioning pagination and the status parameter by noting the confirmed default.

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 provides a specific verb (List) and resource (incoming/received transaction history) and clarifies scope with 'incoming'. However, it does not explicitly differentiate from sibling tools like 'list_transactions' (which likely lists all transactions) or 'get_incoming_summary', leaving the agent to infer the distinction.

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 default behavior ('Returns confirmed incoming transfers by default'), which implies the status parameter's default value. However, it lacks explicit guidance on when to use this tool versus 'list_transactions' or other siblings, and does not state prerequisites like wallet session requirements.

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