Skip to main content
Glama

portal_solana_get_analytics

Retrieve Solana network health snapshot with throughput, fees, wallet activity, and optional top-program analytics.

Instructions

Get the big picture for Solana throughput, fees, wallet activity, and optional top-program usage.

COMMON USER ASKS:

  • Solana network snapshot

  • Include top programs

FIRST CHOICE FOR:

  • the big picture for Solana right now

WHEN TO USE:

  • You want the big picture for Solana right now.

  • You want a network health snapshot for Solana.

  • You want throughput, fee, success-rate, or top-program analytics rather than raw records.

DON'T USE:

  • You want chart buckets or raw transaction/instruction records.

EXAMPLES:

  • Solana network snapshot: {"network":"solana-mainnet","timeframe":"1h"}

  • Include top programs: {"network":"solana-mainnet","timeframe":"1h","include_programs":true}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoExecution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews.deep
cursorNoContinuation cursor for paginating top_programs
networkNoNetwork name (default: solana-mainnet)solana-mainnet
timeframeNoTime range. Accepts compact durations like '15m' or natural phrases like 'past 30 minutes'. Optional; defaults to a 1h analysis window.
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
program_limitNoMax top-program rows to return per page when include_programs is enabled
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
response_formatNoResponse format: 'summary' (high-level metrics), 'compact' (core sections), 'full' (complete analytics).full
include_programsNoInclude top programs by instruction count (requires an extra instruction scan and is slower)
include_compute_unitsNoInclude average compute-unit stats across the full range (disabled by default for speed)
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that including top programs requires an extra scan and is slower, and that include_compute_units is disabled by default for speed. However, it does not explicitly state whether the operation is read-only or mention any side effects, rate limits, or authentication needs.

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 sections like 'FIRST CHOICE FOR', 'WHEN TO USE', 'DON'T USE', and 'EXAMPLES'. It is concise yet informative, front-loading the main purpose, and every sentence adds value without redundancy.

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 the complexity (10 parameters, no output schema), the description covers the tool's purpose, usage guidelines, and behavioral nuances like performance implications. It provides examples but could be more complete by describing the response structure or return value format.

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 description coverage is 100%, so the baseline is 3. The description adds overall context and examples but does not provide additional parameter-level detail beyond what the schema already offers. The examples illustrate correct usage but do not enhance parameter semantics.

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 gets the big picture for Solana throughput, fees, wallet activity, and optional top-program usage. It specifies the verb and resource, and the 'FIRST CHOICE FOR' and sibling tool names distinguish it from other network-specific tools like portal_bitcoin_get_analytics.

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, providing clear context for when to choose this tool over alternatives. It also gives examples of user asks, guiding the AI agent on appropriate scenarios like network health snapshots.

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