Solana MCP Server

get_balance

Retrieve the SOL balance of any Solana wallet address on mainnet, devnet, or testnet.

Instructions

Get the SOL balance of a Solana wallet address

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "get_balance"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	The Solana wallet address (base58 public key)
`network`	No	Solana network to use (defaults to mainnet-beta)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 27, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description indicates a read-only operation (get), which is correct, but provides no additional behavioral details such as rate limits, error handling, or authentication requirements. As annotations are absent, the burden falls on the description, which remains minimal.

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?

Single sentence with no wasted words, front-loaded with the action. Efficient and clear.

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?

For a simple balance check with no output schema, the description is adequate but lacks specifics on return format (e.g., lamports or SOL). Could be more precise given the absence of output schema documentation.

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?

Both parameters are fully described in the schema (100% coverage). The description adds no new meaning beyond 'SOL balance', so 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 clearly states the verb 'Get', the resource 'SOL balance', and the object 'Solana wallet address', distinguishing it from sibling tools like get_token_balance or get_account_info.

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

Usage Guidelines3/5

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

The description implies usage for fetching SOL balance, but does not explicitly provide when-not-to-use or mention alternatives. Lack of exclusions or context on when to prefer this over other getters.

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