Skip to main content
Glama

Prepaid wallet balance

wallet_balance
Read-onlyIdempotent

This organisation's prepaid wallet: balance, what is available after holds for calls in progress, currency, the low-balance alert threshold, auto-recharge status, and prepaid enforcement (whether a low balance is holding calls). Read only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 a closed-world scope, so the "Read only" sentence is largely redundant. The description does add genuine value by naming the data categories returned, including the interpretive detail that prepaid enforcement indicates whether a low balance is currently holding calls. It stops short of stating freshness/caching behavior or whether funds are real-time, which would matter for a balance check.

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 dense sentence plus a two-word safety note. It is front-loaded with the core concept (the wallet and its balance) and then lists the remaining fields efficiently. The final "Read only." fragment is filler given the annotations, but the cost is trivial.

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?

With no output schema, the description carries the burden of describing return values, and it does so thoroughly by enumerating each field the wallet object exposes, including the non-obvious "available after holds" distinction. It is nearly complete for a zero-parameter read; only timing/freshness of the balance is unaddressed.

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; the baseline applies. The description correctly implies a no-argument, organisation-scoped call, matching the empty schema.

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?

The description opens with a specific verb+resource ("This organisation's prepaid wallet") and then enumerates exactly what the tool surfaces: balance, available-after-holds, currency, low-balance alert threshold, auto-recharge status, and prepaid enforcement. This is clearly distinguishable from mutation siblings such as wallet_recharge_link, and an agent knows precisely what it gets back.

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 implied rather than stated: the mention of "whether a low balance is holding calls" suggests the diagnostic scenario (why are calls failing?), but the description never says when to call this versus wallet_recharge_link or billing_summary, nor does it give any exclusions. A reasonable agent can infer intent, but the routing guidance is left to inference.

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.