Skip to main content
Glama

portal_evm_query_token_transfers

Query EVM token transfers by token, sender, or recipient without needing Transfer event signatures. Ideal for checking if a token moved or tracing asset flow.

Instructions

Query token-transfer activity on EVM without needing to remember Transfer event signatures. Best for "did token X move?" and asset-tracing questions.

COMMON USER ASKS:

  • Recent USDC transfers

  • First recent USDC transfer

WHEN TO USE:

  • You want ERC-20 style transfer activity filtered by token, sender, or recipient.

  • You want the fastest answer to a token movement question like "did USDC move?".

  • You are tracing suspicious, stolen, bridged, or exploit-related token movement and need sender/recipient/transaction pivots.

  • You want the easiest raw transfer query on an EVM network.

  • You need the first matching transfer in a bounded window without typing the Transfer topic hash.

DON'T USE:

  • You need arbitrary event logs beyond token transfers.

EXAMPLES:

  • Recent USDC transfers: {"network":"base-mainnet","timeframe":"1h","token_symbols":["USDC"],"limit":20}

  • First recent USDC transfer: {"network":"base-mainnet","timeframe":"1h","token_symbols":["USDC"],"scan_order":"earliest","limit":1}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax transfers
cursorNoContinuation cursor from a previous response
networkNoNetwork name or alias. Optional when continuing with cursor.
to_blockNoEnding block number. RECOMMENDED: <10k blocks for fast responses.
timeframeNoTime range (e.g., '1h', '24h'). Alternative to block numbers.
from_blockNoStarting block number
scan_orderNoWhich side of the block window to scan first. Use earliest for first-transfer questions.latest
to_addressesNoRecipient addresses
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
token_symbolsNoToken symbols to resolve via open token-list data, e.g. ["USDC"]. Merges with token_addresses.
from_addressesNoSender addresses
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
token_addressesNoToken contract addresses
include_token_infoNoInclude token metadata (symbol, decimals) inline. Avoids separate token metadata lookups.
max_token_symbol_matchesNoMaximum token-list matches to include per token symbol. Use token_addresses for deterministic single-contract filters.
Behavior4/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It explains the tool's purpose (querying transfers, no event signatures needed), scanning order, and timeframe usage. It does not mention potential rate limits, pagination behavior, or whether the tool is read-only, but these are reasonably inferred. Overall, good transparency for a query tool.

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 well-structured with clear sections (common user asks, when to use, don't use, examples). It is concise with no redundant information, and the key advantage is front-loaded in the first sentence. Every sentence adds value.

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

Completeness4/5

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

Given the complexity (15 parameters, no output schema, no annotations), the description covers most aspects: purpose, usage guidelines, parameter hints via examples, and differentiation from siblings. It could mention the output format (e.g., list of transfers with fields) but the tool name and examples provide sufficient context for an AI agent.

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 description coverage is 100%, so baseline is 3. The description adds value by providing usage patterns and examples that show how to combine parameters (e.g., network, timeframe, token_symbols, scan_order for 'first recent USDC transfer'). This contextual guidance goes beyond the individual parameter descriptions.

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 tool queries token transfers on EVM networks, distinguishing it from sibling tools like portal_evm_query_logs which require raw event signatures. It uses specific language ('Query token-transfer activity', 'did token X move?') and highlights the benefit of not needing to remember Transfer event signatures.

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

Usage Guidelines5/5

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

The 'WHEN TO USE' and 'DON'T USE' sections explicitly outline appropriate scenarios (e.g., ERC-20 transfers, tracing, fastest answer) and when to avoid (arbitrary event logs). Examples further clarify usage, and the sibling tool portal_evm_query_logs is implicitly suggested for other events.

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/subsquid-labs/portal-mcp-server'

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