Skip to main content
Glama

portal_substrate_query_calls

Retrieve raw Substrate or Polkadot calls using pallet and call-name filters, with optional inclusion of emitted events, subcalls, or extrinsic context for in-depth blockchain analysis.

Instructions

Query raw Substrate or Polkadot calls with pallet/call-name filters and optional child-call, emitted-event, or extrinsic context.

COMMON USER ASKS:

  • Recent Balances calls

  • Polkadot calls with emitted events

FIRST CHOICE FOR:

  • raw Substrate or Polkadot call rows, especially when you want the events emitted by those calls

WHEN TO USE:

  • You need raw call records on a Substrate network.

  • You want pallet call activity like Balances.transfer_keep_alive or Ethereum.transact.

  • You want calls plus the events emitted by those calls.

DON'T USE:

  • You want events or aggregate analytics rather than call rows.

EXAMPLES:

  • Recent Balances calls: {"network":"polkadot","timeframe":"1h","call_names":["Balances.transfer_keep_alive"],"limit":20}

  • Polkadot calls with emitted events: {"network":"polkadot","timeframe":"1h","call_names":["ParaInherent.enter"],"include_events":true,"limit":20}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax calls to return
cursorNoContinuation cursor from a previous response
networkNoSubstrate network name or alias. Optional when continuing with cursor.
to_blockNoEnding block number
timeframeNoTime range (e.g. '1h', '24h'). Alternative to from_block/to_block.
call_namesNoOptional qualified call names like Timestamp.set or Balances.transfer_keep_alive
from_blockNoStarting block number
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
include_stackNoAttach the parent call stack for each matching call
finalized_onlyNoOnly query finalized blocks
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago".
include_eventsNoAttach events emitted directly by each matching call
response_formatNoResponse format: defaults to 'compact' for chat-friendly output. Compact mode keeps requested subcalls, events, and extrinsic context in a smaller inline shape.
include_subcallsNoAttach direct descendant calls inline for each matching call
include_extrinsicNoAttach the parent extrinsic inline for each matching call
Behavior4/5

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

No annotations exist, but description discloses query behavior, response format options, filtering capabilities, and optional inclusion of events, subcalls, extrinsic, and stack. Does not cover rate limits or pagination limits.

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?

Structured with sections and examples, front-loaded with main purpose. No superfluous text, but length is reasonable given complexity.

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 15 parameters and no output schema, description provides sufficient context on filtering, response options, and examples. Lacks details on output structure but hints at it.

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 description adds marginal value beyond schema. Examples show usage patterns and explain default response_format, but most parameter semantics are already in 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 Substrate or Polkadot calls with filter options, differentiates from the sibling portal_substrate_query_events, and includes specific examples.

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 sections 'FIRST CHOICE FOR', 'WHEN TO USE', and 'DON'T USE' provide clear guidance on appropriate use cases and exclusions.

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