Skip to main content
Glama

portal_evm_get_contract_activity

Get a snapshot of recent activity for any EVM contract, including top callers, interaction volume, and event summaries.

Instructions

Summarize what one specific contract has been doing lately, including recent interactions, unique callers, and optional event activity.

COMMON USER ASKS:

  • Contract activity snapshot

FIRST CHOICE FOR:

  • what one specific contract has been doing lately on an EVM network

WHEN TO USE:

  • You want to ask "what has this contract been doing?" and get a contract-level answer.

  • You want a contract-centric activity summary instead of raw records.

  • You need top callers and interaction volume for one contract.

DON'T USE:

  • You need the underlying raw logs or transactions.

  • You want general recent network activity without naming one contract.

EXAMPLES:

  • Contract activity snapshot: {"network":"base-mainnet","contract_address":"0xabc...","timeframe":"24h"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoExecution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews.deep
networkYesNetwork name or alias
timeframeNoAnalysis period as timeframe or block count. Examples: '1h', '24h', '7d', '3d', '1000'.1000
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_eventsNoInclude event log summary
contract_addressYesContract address to analyze
Behavior3/5

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

No annotations exist, so description must compensate. It describes high-level behavior (summarizes interactions, callers, events) and mentions execution modes ('fast' vs 'deep'), but lacks details on permissions, rate limits, or data freshness.

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?

Well-organized with headings, bullet points, and an example. A few sections could be condensed, but overall it's clear and easy to scan.

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

Completeness3/5

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

Covers purpose and usage well, but lacks information about the return format or structure. With 7 parameters and no output schema, a brief note on expected output would improve completeness.

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 each parameter has a description. The description adds examples and clarifies 'timeframe' vs block count, but largely restates schema info. Baseline 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 the tool summarizes recent contract activity including interactions, unique callers, and events. It uses specific verbs ('summarize', 'analyze') and distinguishes itself from siblings like raw log queries.

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 context. It specifies it's the 'FIRST CHOICE FOR' contract activity snapshots and advises against using when raw logs or general network activity are needed.

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