Solana MCP Server

get_cluster_nodes

Retrieve information about all nodes in the Solana cluster for a specified network. Supports mainnet-beta, devnet, and testnet.

Instructions

Get info about all nodes in the Solana cluster

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": "get_cluster_nodes"
  }
}

Input Schema

Name	Required	Description	Default
`network`	No	Solana network

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 27, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates a read operation ('Get info') but does not disclose what specific information is returned, potential performance implications, or any limitations. This is adequate but lacks depth.

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?

The description is extremely concise, using one short sentence. It front-loads the purpose without waste. However, it could be slightly more informative without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity (1 parameter, no output schema), the description is somewhat complete. However, it does not explain what 'info' entails (e.g., node addresses, version, stake), which could leave an agent uncertain about the data 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%, with the single parameter 'network' having an enum and description. The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 'Get info about all nodes in the Solana cluster' clearly states the tool's purpose with a specific verb ('Get') and resource ('all nodes in the Solana cluster'). It distinguishes itself from sibling tools like get_health or get_slot by targeting cluster nodes specifically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With over 30 sibling tools, there is no mention of context, exclusions, or examples that would help an agent decide when to invoke get_cluster_nodes instead of other get_* tools.

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