Skip to main content
Glama

portal_substrate_get_analytics

Retrieves an analytics snapshot for Substrate or Polkadot activity in a specified timeframe, including event, call, and extrinsic counts plus top event and call names.

Instructions

Analytics snapshot for Substrate or Polkadot activity in an indexed window, with event, call, and extrinsic counts plus top event and call names.

COMMON USER ASKS:

  • Polkadot activity snapshot

  • Big picture for Polkadot activity

  • How is Polkadot doing?

FIRST CHOICE FOR:

  • Polkadot activity analytics in an indexed window

  • how Polkadot is doing in an indexed window

  • analytics snapshot for Polkadot or another Substrate network in an indexed window

WHEN TO USE:

  • You want Polkadot activity analytics in a selected indexed window.

  • You want to ask "how is Polkadot doing in this indexed window?" and get an analytics answer rather than just network freshness metadata.

  • You want a quick Substrate network snapshot or health check.

  • You want top pallet events and calls rather than raw rows.

  • You want to know how a Substrate network is doing in the selected indexed window.

DON'T USE:

  • You need full raw event or call records.

EXAMPLES:

  • Polkadot activity snapshot: {"network":"polkadot","timeframe":"1h"}

  • Big picture for Polkadot activity: {"network":"polkadot","timeframe":"1h"}

  • How is Polkadot doing?: {"network":"polkadot","timeframe":"6h"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoExecution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews.deep
networkNoSubstrate network name (default: polkadot)polkadot
to_blockNoEnding block number
timeframeNoTime range like '1h', '6h', or '24h'. Default: '1h'
from_blockNoStarting block number (use this OR timeframe)
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
section_limitNoMax rows to keep in ranked event and call sections
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago".
response_formatNoResponse format: 'summary' (headline metrics only), 'compact' (core sections), 'full' (full dashboard payload)full
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 indicates the tool is a read-only 'snapshot' or 'health check' with no mention of side effects, which is adequate for an analytical tool. It also describes execution depth modes ('fast' vs 'deep') and response formats, adding behavioral context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose with multiple sections ('COMMON USER ASKS', 'FIRST CHOICE FOR', 'WHEN TO USE', 'DON'T USE') that overlap in content. It could be streamlined without losing clarity. However, the key information is front-loaded and the structure is logical.

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 no output schema, the description explains the return value (counts and top names) and mentions response formats. It also provides examples that illustrate expected inputs. The description covers the essential aspects for an agent to understand the tool's purpose and outputs, though it could be slightly more comprehensive about edge cases.

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 does not significantly enhance parameter understanding beyond the schema's own descriptions, though the 'EXAMPLES' section shows typical usage patterns, which adds some value. The parameter descriptions in the schema are already detailed.

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 provides an 'analytics snapshot' with event, call, and extrinsic counts plus top names. It differentiates from sibling tools like portal_substrate_query_calls and portal_substrate_query_events by specifying that it returns aggregated analytics rather than raw rows, and provides examples of common user asks.

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 includes explicit 'WHEN TO USE' and 'DON'T USE' sections, listing specific scenarios such as wanting a quick network health check or top pallet events vs. needing full raw records. It also indicates it is the first choice for polkadot activity analytics, providing clear context for tool selection.

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