Skip to main content
Glama

Get live stats for one Solana validator by vote account or identity pubkey.

solana_validators_get_validator
Read-onlyIdempotent

Get live stats for one Solana validator by vote account or identity pubkey. Pass vote (vote account pubkey) or identity (node identity pubkey). Returns stake in SOL with share and rank, commission, delinquency, how many slots its last vote is behind the cluster, vote credits for each of the last 5 epochs per SOL staked, as a percentage of the cluster median (100 = median; approximate, as it uses today's stake), and current-epoch leader slots, blocks produced and skip rate next to the cluster's. Unknown keys return 404. Costs $0.001 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_get_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
voteNoVote account pubkey (base58) (e.g. JDMq8hxZnad2smKLGkFbfg8zVMZHKQcMugD4tMR9u2da)
identityNoValidator identity (node) pubkey (base58); use instead of vote

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.3/5.0
Behavior5/5

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

Well beyond the annotations, which already declare readOnly, idempotent, non-destructive and closed-world. The description discloses the 404 for unknown keys, the price ($0.001 per call via x402 in USDC on Base), the free-tier allowance, that failed calls are not charged, and what happens without x402 support. That is exactly the payment/error behavior an agent needs before calling a paid tool.

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 and key choice, then results, errors, and pricing in a logical order, with no filler sentences. It is dense but every clause carries operational information; the long enumeration of returned metrics could be tightened since an output schema exists.

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 a paid, networked lookup with an output schema, the description covers cost, error behavior, free-tier caveats, and source data provenance. Its main redundancy is restating return fields already captured by the output schema, but that redundancy is informative rather than harmful.

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 both parameters are already documented in the schema, making the 3 baseline appropriate. The description restates the vote/identity choice but adds no format or precedence detail beyond the schema's 'use instead of vote'. It also does not address what happens when neither optional parameter is supplied.

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?

States a specific verb and resource ('Get live stats for one Solana validator') and immediately names the two lookup keys. An agent can distinguish this from list_validators or get_network_summary purely from the description, since it is explicitly scoped to a single validator.

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?

Gives clear usage instructions: pass 'vote' or 'identity', with the schema noting identity should be used instead of vote. It also covers the payment fallback path when x402 is unavailable. It does not explicitly route to sibling tools (e.g., use list_validators for many validators), so it falls short of full alternative-naming 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