Skip to main content
Glama

portal_debug_query_blocks

Query raw block records directly for EVM, Solana, or Bitcoin to debug Portal coverage or access block-level fields.

Instructions

ADVANCED: Query raw block records directly for EVM, Solana, or Bitcoin.

COMMON USER ASKS:

  • Recent Base blocks

WHEN TO USE:

  • You are debugging Portal coverage or block-level fields.

  • You need raw block records instead of transactions, logs, or summaries.

DON'T USE:

  • You are answering a normal end-user question; prefer recent activity, time series, or raw transaction tools first.

EXAMPLES:

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax blocks to return (default: 20). Note: Lower default for MCP to reduce context usage.
cursorNoContinuation cursor from a previous response
networkNoNetwork name or alias. Optional when continuing with cursor.
to_blockNoEnding block number
timeframeNoTime range (e.g., '1h', '24h'). Alternative to from_block/to_block.
from_blockNoStarting block number (use this OR timeframe)
field_presetNoField preset for EVM datasets: 'minimal' (number+timestamp+gas), 'standard' (+hash+miner+size), 'full' (all block fields). Ignored for Solana/Bitcoin.standard
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
finalized_onlyNoOnly query finalized blocks
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
include_l2_fieldsNoInclude L2-specific fields (auto-detected for L2 chains)
Behavior3/5

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

The description labels the tool as 'ADVANCED' and 'debugging' but does not disclose behavioral traits beyond that, such as side effects, data volume implications, or response structure. With no annotations, more detail would be beneficial.

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 (main statement, common asks, when/don't use, examples). It is concise and every sentence adds 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?

Given 11 parameters and no output schema or annotations, the description could be more complete. It explains purpose and usage well but lacks details on return format, pagination, or potential limitations.

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 coverage is 100%, so the baseline is 3. The description provides an example usage (network, timeframe, limit) but does not add significant new meaning beyond the parameter descriptions in the schema.

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 raw block records for EVM, Solana, or Bitcoin. It distinguishes from siblings by specifying raw block records instead of transactions, logs, or summaries.

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?

Explicit 'WHEN TO USE' and 'DON'T USE' sections provide clear guidance on when to use this tool versus alternatives, including specific examples like debugging coverage or raw block needs, and when to prefer other tools.

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