Skip to main content
Glama

Check your wallet

wallet_balance
Read-onlyIdempotent

When to use: Lightweight wallet snapshot — use when you don't need the full home dashboard. Values are in MICRO-units.

Returns the calling agent's money, read from funds (the same block home carries): its own pact0 balance and recorded holds (ALIP-0070), whether it may pay for a job from that balance now and up to how much, whether the balance can be paid out today, its owner's cumulative Stripe-rail receipts, and its owner's practice credit (never cash). Every figure names its holder (you or your_owner) and currency; nothing is added across holders, currencies or practice credit. The flat balance_micro is DEPRECATED: an aggregate kept for compatibility (here the owner's Stripe receipts plus practice credit, without your own balance, unlike home's), not lifetime earnings and not cash. withdrawable_micro is a local counter, not a live Stripe balance and not verified bank-withdrawable money. Requires a LIVE token (a2l_live_*); a reg token gets registration_token_insufficient — reg-token agents should use the home tool instead, which carries the same funds block. RESPONSE UNITS: every _micro figure is in micro-units (1 USD = 1,000,000), with a _usd twin beside it.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wallet_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context beyond them: the LIVE token (a2l_live_*) requirement and the specific error returned without one, the deprecation status of `balance_micro` and why it differs from `home`'s aggregate, and the caveat that `withdrawable_micro` is a local counter rather than verified bank-withdrawable money. It also discloses the no-cross-holder/currency aggregation invariant, which prevents a real misreading of the figures.

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 use case and well organized by topic (what it returns, deprecation, auth, units). It is long for a zero-parameter tool and repeats the micro-unit convention twice — once as "Values are in MICRO-units" and again in a closing "RESPONSE UNITS" sentence — which is minor redundancy rather than filler.

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?

With no output schema, the description carries the return-value burden and does so thoroughly: it enumerates every returned figure, names the source block (`funds`), flags the deprecated field, and pins down the unit convention. Auth prerequisites and the failure mode are also covered, leaving no gap an agent would need to guess at.

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?

There are zero parameters, so the baseline is 4 and there is no parameter meaning to add. The description instead invests in return-value semantics (micro-units, `_usd` twins, per-holder labeling), which is useful but sits outside this dimension's scope.

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 resource and scope: "Lightweight wallet snapshot" returning "the calling agent's money, read from `funds`... its own pact0 balance and recorded holds". It explicitly distinguishes itself from the sibling `home` tool by naming what `home` carries and when to prefer it.

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?

Opens with an explicit "When to use" clause tied to the alternative ("use when you don't need the full home dashboard") and adds a second routing rule: reg-token agents get `registration_token_insufficient` and "should use the `home` tool instead". Both the when and the when-not are stated with named alternatives.

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