Skip to main content
Glama

Agent Tollbooth 402

Check Wallet Credit Balance

tollbooth_wallet_balance
Read-onlyIdempotent

Inspect an agent wallet credit balance, status, and remaining UTC daily spend cap. Read-only lookup.

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": {
      "walletId": "<walletId>"
    },
    "name": "tollbooth_wallet_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletIdYesAgent wallet identifier to inspect (e.g., wallet_demo).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description's 'Read-only lookup' merely restates readOnlyHint; the genuine added value is the disclosure that status and a UTC-scoped daily spend cap are returned, not just a balance. No error behavior for an unknown walletId is described.

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?

Two compact sentences with no filler, and the primary purpose is front-loaded before the read-only qualifier. Nothing is wasted, though the second sentence is largely redundant with the annotations.

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?

There is no output schema, so the description must convey return contents, and it does by naming balance, status, and remaining daily cap. For a single-parameter, fully annotated, idempotent read tool, this is nearly complete; only edge-case behavior for invalid or unknown wallet IDs is missing.

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% with a single documented walletId parameter, so the schema already carries the burden and the baseline of 3 applies. The description adds only the phrase 'agent wallet', which aligns with the schema's 'Agent wallet identifier' example without extending it.

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?

The description gives a specific verb and resource ('Inspect an agent wallet credit balance') and enumerates the three values returned (credit balance, status, remaining UTC daily spend cap). It does not name any sibling tool, but the read-only inspection framing makes it distinguishable from top-up, receipt, quote, and verification tools.

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?

The phrase 'Read-only lookup' implies usage — reach for this when you only need to check state — but there is no explicit when-to-use, no prerequisite statement (e.g., wallet must exist), and no exclusion pointing to a sibling. Guidance is inferred rather than stated.

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.