Skip to main content
Glama
Sign In

Tollkit

by io.github.UltraStarz
OverviewDiscussionsAdmin

Wallet balance

wallet_balance
Read-only

Check a wallet's balances on Base, Ethereum or Solana: native ETH or SOL, USDC (plus USDT on Ethereum and Solana), and any token contracts or SPL mints you list (up to 20), with symbols and decimals applied. Read live from the chain.

$0.002 USDC per call over x402. Failed calls cost nothing. Call without payment to get a quote.

When to use: You need what a wallet holds, in token amounts. Use instead: wallet_portfolio for USD values and a total; check_my_balance (free) for your own USDC on Base. Parameters: address is required. chain: base (default), ethereum or solana; the address format must match. tokens: up to 20 extra ERC-20 contracts or SPL mints to include. Returns: native coin, USDC (USDT on Ethereum and Solana) and the tokens you listed, each with symbol, decimals and amount.

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

Input Schema

NameRequiredDescriptionDefault
chainNo"base" (default), "ethereum" or "solana".
tokensNoExtra ERC-20 contracts (SPL mints on Solana) to include.
addressYes0x address on Base/Ethereum, or base58 address on Solana.
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"0x-prefixed 40-hex-character address."New value: +"0x address on Base/Ethereum, or base58 address on Solana."
    • changedInput schema / properties / chain / description
      Previous value: -"\"base\" (default) or \"ethereum\"."New value: +"\"base\" (default), \"ethereum\" or \"solana\"."
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "base",
-  "ethereum"
-]New value: +[
+  "base",
+  "ethereum",
+  "solana"
+]
    • changedInput schema / properties / tokens / description
      Previous value: -"Extra ERC-20 contract addresses to include."New value: +"Extra ERC-20 contracts (SPL mints on Solana) to include."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true and openWorldHint=true; the description adds the commercially critical behavior an agent cannot infer: $0.002 USDC per call over x402, failed calls free, and the two-step quote-then-sign flow via omitting `payment`. It also discloses that values are read live from chain rather than cached.

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 the capability, then labeled When-to-use / Use-instead / Parameters / Returns sections, so an agent can skip to the relevant block. Some redundancy exists — the opening paragraph and the Parameters block both restate the chain options and the 20-token cap.

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

Completeness5/5

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

No output schema exists, so the description must describe return values and does: native coin, USDC (USDT on Ethereum/Solana), and listed tokens each with symbol, decimals and amount. Payment, failure, and pricing semantics are all covered, leaving nothing an agent needs before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real cross-parameter meaning: the chain default is base and "the address format must match" the chain, which is a constraint an agent could miss by reading each field in isolation. The token cap of 20 is restated rather than extended, so it stops short of a 5.

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 ("Check a wallet's balances") and immediately bounds scope: three named chains, native coin, USDC/USDT, plus up to 20 caller-supplied token contracts or SPL mints. This is distinguishable at a glance from wallet_portfolio and check_my_balance, which the description itself names.

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

Usage Guidelines5/5

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

Explicit "When to use: You need what a wallet holds, in token amounts" plus a "Use instead" line routing to wallet_portfolio for USD totals and to check_my_balance for the caller's own USDC on Base. Both alternatives are named with the condition that selects them.

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

All Tollkit toolsInspect
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