Crypto, web, finance and app data tools

Solana Wallet Balance

solana_balance

SOL and SPL token balances of a Solana wallet (Token and Token-2022), with USD values and total where a price is known. Use to check a Solana wallet or confirm a payment arrived.

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

Input Schema

Name	Required	Description	Default
`address`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations the description carries the burden, and it does disclose meaningful traits: the token programs covered, that USD values and a total are computed, and the important caveat that valuation appears only 'where a price is known'. It omits auth/rate-limit/error behavior, but the tool is a read-only lookup where those gaps are modest.

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?

Two tight sentences, with the substantive capability statement front-loaded before the usage hint. No filler or restatement of the tool name.

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?

An output schema exists and the tool takes a single required input, so the description needn't explain return values. What remains thin is address formatting guidance and any failure-mode expectation; otherwise an agent has enough to invoke it correctly.

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?

There is only one parameter and schema description coverage is 0%, so the description must carry the meaning. Saying balances are 'of a Solana wallet' implies the address is a Solana wallet address, but it never states the expected format (base58, length) or what happens for an invalid/malformed address.

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 states a specific verb/scope (returns SOL and SPL token balances), names the resource (a Solana wallet), and pins down chain and token standards (Token and Token-2022), which cleanly separates it from siblings such as evm_wallet_balance, erc20_balance, or bitcoin_address.

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 two concrete use cases ('check a Solana wallet', 'confirm a payment arrived'), which is clear situational context. It does not name alternatives or exclusions, so it falls short of a 5.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?