Skip to main content
Glama

Wallet balance

wallet_balance
Read-only

Get SOL balance and all token balances for a Solana wallet. Lightweight check — use before transactions to verify sufficient funds. Costs $0.001 USDC per call.

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": {
      "walletAddress": "<walletAddress>"
    },
    "name": "wallet_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYesSolana wallet address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new operational context: a per-call cost of $0.001 USDC and the 'lightweight' cost profile, which affects call budgeting. It does not cover invalid/empty-wallet behavior.

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?

Three short sentences with no waste: what it returns, when to use it, what it costs — all front-loaded, most important first.

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?

No output schema, but the description states the return contents (SOL balance + all token balances) well enough for an agent to use the result. Cost and use-case are covered; error/edge behavior is the only real gap.

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% and the single walletAddress parameter is fully documented in the schema (base58 Solana address). The description adds nothing about the parameter, so the baseline 3 applies.

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?

Specific verb+resource: SOL balance plus all token balances for a single Solana wallet. It is clearly distinguishable from wallet_pnl/wallet_profile by being a raw balance read, though those siblings are never named.

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 an explicit usage condition — 'use before transactions to verify sufficient funds' — which tells the agent when to reach for this. It stops short of naming alternatives or exclusions (e.g. use token_holders for holder data).

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