Skip to main content
Glama

Get live Solana network health: epoch progress, validator counts, stake concentration and skip rate.

solana_validators_get_network_summary
Read-onlyIdempotent

Get live Solana network health: epoch progress, validator counts, stake concentration and skip rate. Returns the current epoch and its progress, active and delinquent validator counts, total active stake in SOL, the delinquent stake share, the Nakamoto coefficient (fewest validators holding over a third of stake), median commission, cluster block production and skip rate so far this epoch, and median and best vote credits per SOL staked in the last complete epoch. Use it as the baseline when judging a single validator. Free, no payment needed. Source: Solana mainnet-beta (public chain state via JSON-RPC), Public on-chain data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "solana_validators_get_network_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNoResult: a list of applications for search and nearby tools, one record or summary object otherwise
metaYesPaging and query details, e.g. limit, offset, has_more, count
attributionYesSource attribution; keep it when presenting the data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: the tool is free with no payment required, the data source is Solana mainnet-beta via JSON-RPC, and the time windows are pinned ('so far this epoch', 'last complete epoch'). It could still say more about snapshot freshness or caching.

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?

Front-loaded with purpose, then returns, then usage, then cost and provenance — a sensible ordering. The return-field list is dense and slightly overlaps the title, but each clause carries distinct information rather than padding.

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?

For a zero-parameter, read-only aggregate query with an output schema, the definition covers everything an agent needs to select and call it: what it returns, its time semantics, that it costs nothing, and its data source. No material gap remains.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-arg tool applies. Nothing in the description misleads about inputs.

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 opens with a specific verb+resource ('Get live Solana network health') and immediately enumerates the scope: epoch progress, validator counts, stake concentration, skip rate. This is clearly a cluster-wide aggregate, which distinguishes it from the per-validator siblings without needing to name them.

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?

It gives an explicit use case: 'Use it as the baseline when judging a single validator,' which routes the agent here before or alongside solana_validators_get_validator. It stops short of naming that sibling or stating when-not to call it, so it's clear context without full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources