Skip to main content
Glama

portal_substrate_query_events

Filter and retrieve raw Substrate or Polkadot event rows by pallet and event name, with optional parent call or extrinsic context. Supports time ranges and block numbers.

Instructions

Query raw Substrate or Polkadot event rows with pallet/event-name filters and optional parent call or extrinsic context.

COMMON USER ASKS:

  • Balances.Transfer events on Polkadot

FIRST CHOICE FOR:

  • raw Substrate or Polkadot event rows with optional parent call or extrinsic context

WHEN TO USE:

  • You need raw event records on a Substrate network.

  • You want pallet-level event activity like Balances.Transfer or Contracts.ContractEmitted.

  • You want event rows first, even if the network is a Polkadot-family chain.

DON'T USE:

  • You want calls or aggregate analytics rather than event rows.

EXAMPLES:

  • Balances.Transfer events on Polkadot: {"network":"polkadot","timeframe":"1h","event_names":["Balances.Transfer"],"limit":20}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax events 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.
from_blockNoStarting block number
event_namesNoOptional qualified event names like Balances.Transfer or System.ExtrinsicSuccess
include_callNoAttach the emitting call inline when the event has call context
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
include_stackNoAttach the parent call stack when the event has nested call context
finalized_onlyNoOnly query finalized blocks
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago".
response_formatNoResponse format: defaults to 'compact' for chat-friendly output. Compact mode keeps requested extrinsic or call context in a smaller inline shape.
include_extrinsicNoAttach the parent extrinsic inline for each matching event
Behavior3/5

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

No annotations are provided, so the description bears the full burden. It describes what the tool does but does not disclose behavioral traits such as rate limits, authentication requirements, or performance characteristics. The description implies a read-only operation, but lacks explicit safety guarantees.

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 labeled sections, making it easy to scan. The opening line is front-loaded with the core purpose. However, there is slight redundancy (e.g., 'raw Substrate or Polkadot event rows' appears multiple times), preventing a perfect score.

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

Completeness5/5

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

Given the high parameter count (14) and no output schema, the description provides ample context: usage guidance, an example, and notes on optional parameters like include_call and include_stack. It fully equips the agent to understand when and how to use the tool.

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%, meaning the input schema already describes all parameters. The description adds a usage example and common user asks, but does not provide new semantic meaning beyond what the schema offers. The baseline of 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 it queries raw Substrate or Polkadot event rows with pallet/event-name filters and optional context. It includes a common user ask and an example, distinguishing it from sibling tools like portal_substrate_query_calls.

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 appropriate usage, including when to avoid the tool. It implies alternatives by mentioning 'calls or aggregate analytics' in the don't-use clause, and the sibling tool list provides concrete alternatives.

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