Skip to main content
Glama

List Solana validators ranked by stake, vote credits, skip rate or commission, with filters.

solana_validators_list_validators
Read-onlyIdempotent

List Solana validators ranked by stake, vote credits, skip rate or commission, with filters. For choosing where to stake or comparing validators. sort is stake (default), credits (vote credits per SOL in the last complete epoch, as % of the cluster median), skip_rate (current epoch, lowest first; validators with no leader slots yet come last) or commission (lowest first). Filters: max_commission (percent), min_stake_sol, include_delinquent (default false). Returns up to limit rows (default 20, max 50) and the number matched. Costs $0.002 per call, paid via x402 in USDC on Base; the first 3 paid-tool calls per day are free for MCP clients while a shared daily allowance lasts. Without x402 support, later calls return the payment requirements as an error result. Failed calls are not charged. 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_list_validators"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOne of stake, credits, skip_rate, commission (default stake) (e.g. credits)
limitNoRows to return, 1 to 50 (default 20) (e.g. 10)
min_stake_solNoOnly validators with at least this much active stake in SOL (e.g. 100000)
max_commissionNoOnly validators with commission at most this percent (e.g. 5)
include_delinquentNotrue to include delinquent validators (default false)

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
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description still adds material operational context: $0.002 per call via x402 in USDC on Base, a free tier of 3 paid calls per day while an allowance lasts, error-result payment requirements for clients without x402, and that failed calls are not charged. It also discloses the data source (Solana mainnet-beta public chain state via JSON-RPC) and the return volume cap.

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?

It is front-loaded with purpose, then sort semantics, then filters, then cost, which is a sensible order for an agent skimming it. The billing sentences are dense but each carries decision-relevant information; the only mild redundancy is restating defaults already present in the schema.

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 paid, filtered read tool with 5 parameters and an output schema, the definition covers cost, free tier, failure semantics, data source and row limits, so an agent can call it correctly. Return-value shape is legitimately left to the output schema, though the mention of 'the number matched' sits alongside that schema without extra detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Beyond the schema, the description defines what 'credits' actually measures (vote credits per SOL in the last complete epoch, as a percentage of the cluster median) and gives sort direction for skip_rate and commission ('lowest first') plus the delinquent-validator ordering rule. The schema only lists the accepted values, so the description adds substantial interpretive meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition states a specific verb and resource ('List Solana validators') plus the ranking dimensions and filter set, which makes it clearly distinct from get_validator (single record) and get_network_summary (aggregate stats). It stops short of the 5 mark because it never explicitly names a sibling or states a boundary, leaving differentiation to inference from the title.

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 a clear use case ('For choosing where to stake or comparing validators'), which tells the agent when this tool is appropriate. There is no explicit when-not guidance or named alternative for the single-validator lookup case, so it falls short of full routing guidance.

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