Skip to main content
Glama

portal_evm_query_transactions

Query raw EVM transactions with filters for sender, receiver, method, transaction type, and include logs, traces, or state diffs for investigation.

Instructions

Query raw EVM transactions with optional logs, traces, state-diff context, and evidence pivots for transaction-level investigations.

COMMON USER ASKS:

  • Recent Base transactions

  • Filter by sender

  • First EIP-2930 transaction from Berlin fork

WHEN TO USE:

  • You need raw transaction records on an EVM network.

  • You want chain-specific transaction fields or include flags that convenience tools do not expose.

  • You need exact transaction evidence for an investigation, including sender, receiver, transaction hash, logs, traces, or failed calls.

  • You need to find the first transaction matching a raw field condition such as transaction type 0x1 from a known block.

  • You need top-N raw transactions ranked by value, gas used, or effective gas price.

  • You need top senders or receivers from a bounded transaction window.

  • You want common method names such as transfer, approve, deposit, or withdraw instead of remembering sighashes.

  • You want calls to a token contract by symbol, such as transfer calls to USDC, without hardcoding token addresses.

DON'T USE:

  • You only need a quick recent feed or wallet-level summary.

EXAMPLES:

  • Recent Base transactions: {"network":"base-mainnet","timeframe":"1h","limit":20}

  • Filter by sender: {"network":"ethereum-mainnet","timeframe":"6h","from_addresses":["0xabc..."],"limit":20}

  • First EIP-2930 transaction from Berlin fork: {"network":"ethereum-mainnet","from_block":12244000,"transaction_type":"0x1","scan_order":"earliest","limit":1,"field_preset":"minimal"}

  • Largest recent calls to a resolved token contract: {"network":"base-mainnet","timeframe":"1h","to_token_symbols":["USDC"],"method":"transfer","order_by":"gas_used_desc","limit":5}

  • Top senders by transaction count: {"network":"base-mainnet","timeframe":"1h","aggregate_by":"sender","aggregate_metric":"count","limit":10}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax transactions (default: 20, max: 200). Note: Lower default for MCP to reduce context usage.
cursorNoContinuation cursor from a previous response
methodNoFILTER: Common EVM method alias or 4-byte sighash. Examples: "transfer", "approve", "transferFrom", "deposit", "withdraw". Merges with sighash.
networkNoNetwork name or alias. Optional when continuing with cursor.
sighashNoFILTER: Function sighash (4-byte hex, e.g., '0xa9059cbb' for transfer). Optional if limit <=100.
order_byNoOptional ranking for top-N questions. Use value_desc, gas_used_desc, or effective_gas_price_desc.chronological
to_blockNoEnding block number. RECOMMENDED: <5k blocks for fast (<500ms) responses. Larger ranges may be slow.
timeframeNoTime range (e.g., '24h', '7d'). Alternative to from_block/to_block. Supported: 1h, 6h, 12h, 24h, 3d, 7d, 14d, 30d. Large ranges OK with low limit (<=100).
from_blockNoStarting block number (use this OR timeframe). Large ranges OK with low limit (<=100).
last_nonceNoMaximum nonce
scan_orderNoWhich side of the block window to scan first. Normal previews default to latest; transaction_type searches default to earliest, so "first tx type 0x1 from block N" scans forward from from_block.
first_nonceNoMinimum nonce
aggregate_byNoOptional bounded aggregation for top sender/receiver questions. Returns ranked address rows instead of raw transactions.
field_presetNoField preset: 'minimal' (from/to/value+block, ~70% smaller), 'standard' (hash+gas+timestamp), 'full' (includes input data hex, largest). Use 'minimal' to reduce context usage.standard
include_logsNoInclude logs emitted by transactions
min_gas_usedNoFILTER/RANKING: Minimum receipt gasUsed. Accepts decimal or hex string.
to_addressesNoFILTER: Recipient addresses (typically contracts being called, or wallets receiving ETH). Optional if limit <=100.
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
min_value_weiNoFILTER/RANKING: Minimum native token value in wei. Accepts decimal or hex string.
finalized_onlyNoOnly query finalized blocks
from_addressesNoFILTER: Sender addresses (wallets or contracts that initiated the transaction). Optional if limit <=100.
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
include_tracesNoInclude traces for transactions
max_scan_blocksNoSafety cap for first/last/ranked client-side scans. Default: min(window, 10000 blocks).
response_formatNoResponse format: defaults to 'compact' for chat-friendly output, or stays 'full' when inline logs, traces, or state diffs are requested. Use 'summary' for counting or profiling.
aggregate_metricNoMetric used with aggregate_by. count ranks by tx count; value by total native value; gas_used by total gas used; effective_gas_price by max effective gas price.count
to_token_symbolsNoResolve token symbols via open token-list data and merge them into to_addresses, e.g. transfer/approve calls to USDC.
transaction_typeNoFILTER: EVM transaction type. Accepts decimal or hex strings such as 0, 1, 2, "0x0", "0x1", "0x2". Applied client-side while streaming Portal results; use with scan_order="earliest" and from_block to find the first typed transaction.
contract_creationNoFILTER: true returns contract-creation transactions; false excludes them. Useful for "first contract creation from this wallet".
include_l2_fieldsNoInclude L2-specific fields
from_token_symbolsNoResolve token symbols via open token-list data and merge them into from_addresses. Rare, but useful for token-contract-originated transactions.
transaction_statusNoFILTER: Transaction receipt status. Use "success"/1 or "failed"/0 for failed/reverted transaction searches.
include_state_diffsNoInclude state diffs caused by transactions
max_token_symbol_matchesNoMaximum token-list matches to include per token symbol. Use from_addresses/to_addresses for deterministic single-contract filters.
min_effective_gas_price_weiNoFILTER/RANKING: Minimum effectiveGasPrice in wei. Accepts decimal or hex string.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It adequately describes the query behavior, including optional includes and aggregation, but does not explicitly state that it is a read-only operation (though implied). It otherwise is transparent about capabilities and constraints.

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 well-structured with clear sections (COMMON USER ASKS, WHEN TO USE, DON'T USE, EXAMPLES) and front-loaded with the main purpose. Though verbose, each section adds value without redundancy. Minor improvement could be trimming the examples further.

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 35 parameters, no output schema, and no annotations, the description covers all major use cases with examples and guidelines. It addresses parameter combinations, limits, and field presets. However, it does not detail the output format or pagination behavior beyond cursor, which is left to the schema.

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 coverage is 100%, so baseline is 3. The description adds significant value by grouping parameters into common use cases, providing example JSON values, and explaining advanced features like token symbol resolution and aggregation. This goes beyond the schema 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 it queries raw EVM transactions with optional context like logs, traces, and state diffs. It distinguishes from sibling tools like portal_evm_query_logs and portal_evm_query_token_transfers by focusing on raw transaction records and exposing chain-specific fields.

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 description provides explicit 'WHEN TO USE' and 'DON'T USE' sections, listing specific use cases (e.g., raw transaction records, first transactions by type, top-N by metrics) and excluding quick feeds or wallet summaries. It also includes concrete examples for each scenario.

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