SQD

Official

by subsquid-labs

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Analyze Ethereum and Base activity

portal_evm_get_analytics

Read-only

Retrieve a network-wide EVM analytics overview, including ranked top contracts and key activity metrics. Ideal for identifying the most active contracts on networks like Base or Optimism.

Instructions

Get the big picture for network-wide EVM activity with ranked contracts and compact overview metrics.

COMMON USER ASKS:

Top contracts on Base

FIRST CHOICE FOR:

the big picture for activity on an EVM network like Base or Optimism

WHEN TO USE:

You want the big picture for activity on an EVM network.
You want the most active contracts on an EVM network.
You want an analytics-style network overview instead of a raw record list.

DON'T USE:

You need chart buckets over time rather than ranked entities.

EXAMPLES:

Top contracts on Base: {"network":"base-mainnet","timeframe":"1h","limit":10}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews.	deep
`limit`	No	Number of top contracts to return (default: 10, max: 100)
`cursor`	No	Continuation cursor from a previous response
`network`	No	Network name (supports short names: 'ethereum', 'polygon', 'base', etc.). Optional when continuing with cursor.
`timeframe`	No	Optional natural time window like '1h' or '24h'
`num_blocks`	No	Number of recent blocks to analyze when timeframe is omitted (default: 50, max: 10000)
`to_timestamp`	No	Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
`from_timestamp`	No	Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
`include_details`	No	Include sample transaction hashes for each contract

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 readOnly/openWorld/non-destructive, so the description only needs to add behavioral expectations. It does: 'ranked contracts', 'compact overview metrics', and 'analytics-style network overview instead of a raw record list' tell the agent what kind of aggregated output to expect. No contradiction with annotations.

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 content is organized into scannable sections and front-loaded with the core summary. It loses a point because 'big picture' is repeated across the summary, FIRST CHOICE FOR, and WHEN TO USE, and the COMMON USER ASKS/FIRST CHOICE sections overlap.

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?

With 100% schema coverage, an output schema, zero required parameters, and read-only annotations, the only missing context is when to choose this tool and what a call looks like—both provided. The example plus exclusions make it complete for an agent to select and invoke.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schemas carry parameter definitions. The description adds value by giving a complete worked example ('Top contracts on Base: network=base-mainnet, timeframe=1h, limit=10') that demonstrates short network names and natural timeframes, which is extra usage meaning beyond 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 one-line summary names a specific resource ('network-wide EVM activity'), a specific artifact ('ranked contracts and compact overview metrics'), and an explicit contrast with 'raw record list'. This clearly separates it from transaction/query/log siblings like portal_evm_query_transactions and from other chains' analytics tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The WHEN TO USE section lists concrete conditions, and the DON'T USE section gives an explicit exclusion for chart-bucket/time-series requests. It doesn't name a specific sibling alternative (e.g., portal_get_time_series or portal_evm_get_ohlc), so it stops just short of the strongest possible guidance.

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