Skip to main content
Glama

spectra_get_address_activity

Scan all pools on a chain to reveal an address's total activity across multiple pools, returning per-pool breakdowns and cross-pool totals. Identifies multi-pool strategies in one call.

Instructions

Scan all pools on a chain (or all chains) for a given address's activity. Returns per-pool breakdown and cross-pool aggregates. Useful for discovering multi-pool strategies without making N manual spectra_get_pool_activity calls.

When investigating a wallet that operates across multiple pools (e.g., a curator or yield farmer diversifying across maturities), this tool reveals the full scope of their on-chain activity in one call.

Each pool's activity is summarized with type breakdown and total volume. Cross-pool totals show the address's aggregate engagement with Spectra.

For deep per-pool analysis (cycle detection, flow accounting, contract detection), use spectra_get_pool_activity with the address parameter on the specific pool of interest. Use spectra_get_portfolio to see current holdings across all pools.

Includes an Observation Coverage section that quantifies blind spots: which pools were scanned, what event types are visible vs invisible (standalone mints, yield claims, and non-Spectra operations are never visible here), and whether activity is concentrated on one chain. Position sizing should assume this scan is incomplete, not comprehensive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe wallet address to scan (0x...)
chainNoSpecific chain to scan. Omit to scan all chains (slower).
min_volume_usdNoMinimum activity volume (USD) per pool to include in results (default 0)
Behavior5/5

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

No annotations provided; description compensates fully by detailing coverage blind spots, invisible event types, and warning that results are incomplete for position sizing. Thoroughly discloses limitations.

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-structured and front-loaded: core function, use cases, comparisons, limitations. Concise but not overly terse; each sentence earns its place. Slight room for tightening.

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?

No output schema, but description explains return structure (per-pool breakdown, cross-pool totals, observation coverage). Addresses completeness concerns bluntly. Sufficient for an aggregation tool.

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 parameters already have descriptions. Description adds minimal extra detail beyond schema (e.g., no elaboration on min_volume_usd beyond default). Meets baseline but no significant added value.

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?

Clearly states the tool scans all pools on a chain for an address's activity, returning per-pool breakdown and cross-pool aggregates. Distinguishes from siblings like spectra_get_pool_activity and spectra_get_portfolio by specifying use cases.

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?

Explicitly recommends use for multi-pool strategy discovery and warns against using for deep per-pool analysis or current holdings, providing alternative tool names. Offers clear context and exclusions.

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/Finanzgoblin/spectra-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server