Skip to main content
Glama
Sign In
waiaas

waiaas

by waiaas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_incoming_transactions

Retrieve incoming transaction history for a wallet with pagination. Filter by chain, status, token, sender, or time range.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_incoming_transactions"
  }
}

Input 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.11.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behaviors. It mentions cursor-based pagination and that only confirmed transfers are returned by default, but does not cover how wallet_id is resolved for multi-wallet sessions or that the operation is read-only (safe to call). It provides basic transparency but could add more context.

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 consists of two concise sentences that deliver essential information without redundancy. Every word contributes value.

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?

For a tool with 10 parameters, no output schema, and no annotations, the description provides a functional overview but omits context like how wallet_id is handled in single vs multi-wallet sessions and what the return format looks like. It is adequate but not comprehensive.

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 each parameter is already documented. The tool description adds minimal extra meaning beyond stating cursor-based pagination and default status. According to the scoring guidelines, baseline 3 is appropriate.

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 verb 'List' and the resource 'incoming (received) transaction history', mentions cursor-based pagination, and specifies the default return of confirmed transfers. This distinguishes it from sibling tools like 'list_transactions' and 'get_transaction'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'list_transactions' or 'get_transaction'. The agent is left to infer from the name and description, but explicit differentiation would improve selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools