SQD

Official

by subsquid-labs

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Find Polkadot events

portal_substrate_query_events

Read-only

Query raw Substrate or Polkadot events by pallet/event name, with optional parent call or extrinsic context. Use it to inspect event activity like Balances.Transfer on any supported network.

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

Name	Required	Description
`limit`	No	Max events to return
`cursor`	No	Continuation cursor from a previous response
`network`	No	Substrate network name or alias. Optional when continuing with cursor.
`to_block`	No	Ending block number
`timeframe`	No	Time range (e.g. '1h', '24h'). Alternative to from_block/to_block.
`from_block`	No	Starting block number
`event_names`	No	Optional qualified event names like Balances.Transfer or System.ExtrinsicSuccess
`include_call`	No	Attach the emitting call inline when the event has call context
`to_timestamp`	No	Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
`include_stack`	No	Attach the parent call stack when the event has nested call context
`finalized_only`	No	Only query finalized blocks
`from_timestamp`	No	Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago".
`response_format`	No	Response format: defaults to 'compact' for chat-friendly output. Compact mode keeps requested extrinsic or call context in a smaller inline shape.
`include_extrinsic`	No	Attach the parent extrinsic inline for each matching event

Output Schema

TableJSON Schema

Name	Required	Description
`_ui`	No	Optional chart, table, and follow-up presentation metadata.
`_llm`	No	Hints that help an AI client locate the primary evidence.
`_meta`	No	Network, block range, timing, and row-count metadata.
`error`	No	Structured failure details when the tool cannot complete the request.
`items`	No	Primary result rows when the tool returns a list.
`value`	No	Primary result when the tool returns a scalar value.
`answer`	No	Concise answer grounded in the returned blockchain data.
`_notice`	No	Important limitation or truncation notice.
`display`	No	Plain-language labels for presenting the result.
`_notices`	No	Important limitations or truncation notices.
`_summary`	No	Human-readable summary of the result.
`_coverage`	No	Completeness of the requested window and result set.
`_evidence`	No	Replayable arguments, exact-data digest, row count, and completeness receipt.
`_ordering`	No	Ordering guarantees for the returned data.
`_execution`	No	Bounded execution and scan details.
`_freshness`	No	Freshness and finality information for the returned data.
`next_steps`	No	Safe follow-up actions and continuation guidance.
`_pagination`	No	Pagination state and an optional continuation cursor.
`investigation`	No	Evidence paths, useful pivots, and result limitations.
`pipes_handoff`	No	Optional SQD Pipes guidance for custom data needs.
`_tool_contract`	No	Tool identity, intent, and supported blockchain families.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedv0.8.3Aug 30, 2026

addedOutput schema / properties / _evidence

Added value: +{
+  "additionalProperties": {},
+  "description": "Replayable arguments, exact-data digest, row count, and completeness receipt.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed7 schema fields changedv0.8.2Aug 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / from_timestamp / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / from_timestamp / type
```
Removed value: -[
-  "number",
-  "string"
-]
```

addedInput schema / properties / to_timestamp / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / to_timestamp / type
```
Removed value: -[
-  "number",
-  "string"
-]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "_coverage": {
+      "description": "Completeness of the requested window and result set."
+    },
+    "_execution": {
+      "additionalProperties": {},
+      "description": "Bounded execution and scan details.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_freshness": {
+      "description": "Freshness and finality information for the returned data."
+    },
+    "_llm": {
+      "description": "Hints that help an AI client locate the primary evidence."
+    },
+    "_meta": {
+      "additionalProperties": {},
+      "description": "Network, block range, timing, and row-count metadata.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_notice": {
+      "description": "Important limitation or truncation notice.",
+      "type": "string"
+    },
+    "_notices": {
+      "description": "Important limitations or truncation notices.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "_ordering": {
+      "description": "Ordering guarantees for the returned data."
+    },
+    "_pagination": {
+      "additionalProperties": {},
+      "description": "Pagination state and an optional continuation cursor.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_summary": {
+      "description": "Human-readable summary of the result.",
+      "type": "string"
+    },
+    "_tool_contract": {
+      "additionalProperties": {},
+      "description": "Tool identity, intent, and supported blockchain families.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_ui": {
+      "description": "Optional chart, table, and follow-up presentation metadata."
+    },
+    "answer": {
+      "description": "Concise answer grounded in the returned blockchain data.",
+      "type": "string"
+    },
+    "display": {
+      "additionalProperties": {},
+      "description": "Plain-language labels for presenting the result.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": {},
+      "description": "Structured failure details when the tool cannot complete the request.",
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "origin": {
+          "type": "string"
+        },
+        "retry_after_ms": {
+          "type": "number"
+        },
+        "retryable": {
+          "type": "boolean"
+        },
+        "suggestions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "summary": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "origin",
+        "summary",
+        "retryable",
+        "suggestions"
+      ],
+      "type": "object"
+    },
+    "investigation": {
+      "additionalProperties": {},
+      "description": "Evidence paths, useful pivots, and result limitations.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "items": {
+      "description": "Primary result rows when the tool returns a list.",
+      "items": {},
+      "type": "array"
+    },
+    "next_steps": {
+      "additionalProperties": {},
+      "description": "Safe follow-up actions and continuation guidance.",
+      "properties": {
+        "actions": {
+          "items": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "continuation": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "custom_data": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "actions"
+      ],
+      "type": "object"
+    },
+    "pipes_handoff": {
+      "description": "Optional SQD Pipes guidance for custom data needs."
+    },
+    "value": {
+      "description": "Primary result when the tool returns a scalar value."
+    }
+  },
+  "type": "object"
+}

First observedv0.7.9Jun 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it returns raw rows, supports pallet/event-name filtering, and can attach parent call or extrinsic context. This helps an agent understand the shape of the query and results.

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-organized with clear sections and front-loaded purpose. There is some redundancy—'FIRST CHOICE FOR' largely repeats the opening sentence—but the WHEN TO USE, DON'T USE, and EXAMPLE sections each earn their place.

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 tool's complexity (14 parameters, output schema present, many siblings), the description is complete for selection and invocation. It covers what the tool does, when to choose it over alternatives, when not to use it, and provides a concrete parameterized example. The output schema handles return-value details.

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 description coverage is 100%, so the schema already documents all 14 parameters. The description adds a helpful example mapping a common ask to parameters (network, timeframe, event_names, limit) and highlights the key filter concept, but it does not meaningfully extend the detailed 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 opens with a specific verb and resource: 'Query raw Substrate or Polkadot event rows with pallet/event-name filters and optional parent call or extrinsic context.' It clearly distinguishes itself from sibling tools by emphasizing 'raw event rows' and 'pallet-level event activity' as opposed to calls or analytics.

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. It states when event rows are the right output and explicitly warns against using this tool for 'calls or aggregate analytics,' which maps directly to sibling tools like portal_substrate_query_calls and portal_substrate_get_analytics.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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