Skip to main content
Glama

check_balance

Read-onlyIdempotent

Retrieve real WBT and official USDT balances for the local Whitechain Sepolia agent wallet. Verify available funds before sending transfers or making x402 API payments.

Instructions

Read real WBT and official USDT balances for the local Whitechain Sepolia agent wallet.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered without the description. The text does add some context beyond them — that the balances are 'real' (not simulated) and belong to the 'local' agent wallet on Whitechain Sepolia — but it says nothing about whether the read hits the chain live, how latency/failure behaves, or what happens if the wallet is unfunded.

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?

One sentence, front-loaded with the verb and the resources, with zero filler. It is arguably slightly over-compressed: qualifiers like 'official' and 'real' carry weight but are not explained, and nothing else about the call is stated.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it only partially does so by naming the two token balances. It does not indicate the response shape (single object, per-asset entries, units/decimals, address included) or whether a failed network read is surfaced as an error or zero balance.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The sentence does usefully narrow the implicit scope to two specific token balances rather than all assets.

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?

States a specific verb ('Read') and resource ('balances') scoped to two named assets (WBT, official USDT) on a named network and wallet ('local Whitechain Sepolia agent wallet'). That is enough to distinguish it from every listed sibling (pay, transfer_*, x402_fetch, spending_report), though it does not explicitly contrast itself with spending_report, which is the nearest analytical sibling.

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?

Usage is only implied: an agent can infer it should call this to inspect funds before a transfer or payment, but the description never says when to use it, when not to, or which sibling answers a related question (e.g. spending_report for historical spend). No prerequisites or exclusions are stated.

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