Skip to main content
Glama

Wallet-Guthaben abrufen

wallet_balance
Read-only

Liefert den aktuellen Wallet-Stand: Guthaben, den für wartende Briefe reservierten Betrag, das verfügbare Guthaben, Tageslimit für Briefe und Kosten, den nächsten Reset-Zeitpunkt sowie das aktuelle Preismodell (Standardpreis oder Mengenstaffel). Bleibt das verfügbare Guthaben unter den geplanten Versandkosten, liefert wallet_topup_link den Link zum Aufladen. EN: Returns the current wallet status: balance, the amount reserved for waiting letters, the available balance, daily cap for letters and costs, and the next reset time. If the available balance is short of the planned send, wallet_topup_link returns the top-up link.

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
reasoningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by detailing the returned fields and the shortfall condition that should route to top-up, though it says nothing about staleness/caching of the balance or auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded and the field enumeration is dense but useful. However, the entire text is duplicated in German and English, doubling length without adding information; a bilingual audience could be served more economically.

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 the response and does so thoroughly, including the pricing-model distinction. Only the undocumented 'reasoning' parameter and the absence of any note on data freshness keep it from being complete.

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?

There is a single optional parameter ('reasoning') with 0% schema description coverage, and the description never mentions it. With such a minimal parameter surface the omission is minor, but the description adds no meaning beyond the 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?

States a specific verb and resource (returns current wallet status) and then enumerates exactly what is returned: balance, reserved amount, available balance, daily caps, next reset, pricing model. It also explicitly distinguishes itself from the sibling wallet_topup_link, which only produces a top-up URL.

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

Usage Guidelines4/5

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

It gives a concrete trigger for the sibling: when available balance falls short of the planned send, use wallet_topup_link. Usage of wallet_balance itself (checking funds before sending letters) is only implied, and no explicit 'do not use for X' exclusions are given.

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.