Skip to main content
Glama

portal_evm_get_analytics

Retrieve a network-wide overview of EVM activity, including ranked top contracts and compact metrics for 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
NameRequiredDescriptionDefault
modeNoExecution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews.deep
limitNoNumber of top contracts to return (default: 10, max: 100)
cursorNoContinuation cursor from a previous response
networkNoNetwork name (supports short names: 'ethereum', 'polygon', 'base', etc.). Optional when continuing with cursor.
timeframeNoOptional natural time window like '1h' or '24h'
num_blocksNoNumber of recent blocks to analyze when timeframe is omitted (default: 50, max: 10000)
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
include_detailsNoInclude sample transaction hashes for each contract
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 adds context that the tool returns ranked contracts and overview metrics, not raw records. However, it does not explicitly disclose mutability or safety, but the name 'get_analytics' implies read-only.

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

Conciseness5/5

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

The description is well-structured with clear sections, front-loaded purpose, and an example. Every sentence adds value, and there is no redundancy or fluff.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description covers purpose, usage, and examples well. It lacks detailed output format, but the example gives some indication of expected results.

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 baseline is 3. The description includes an example that demonstrates typical parameter usage (network, timeframe, limit), complementing the schema but not adding significant new semantic detail.

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 'Get the big picture for network-wide EVM activity with ranked contracts and compact overview metrics,' using a specific verb and resource. It distinguishes from sibling tools like portal_hyperliquid_get_analytics by focusing on EVM networks.

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 'FIRST CHOICE FOR', 'WHEN TO USE', and 'DON'T USE' sections, providing clear guidance on when to choose this tool over others (e.g., for network overview rather than time buckets). It also gives a common user ask example.

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