Skip to main content
Glama

Get wallet balance

get_wallet_balance
Read-only

The organisation's prepaid credit wallet (the twin of ankra org billing wallet): the net position in EUR, whether it is funded, in its grace period, restricted or frozen, the credit lots in the order they will be spent with their expiry, and whether top-ups are open. An organisation never credited reads as absent, which is the free tier, not an empty wallet. Requires billing.read. Read-only; credit is added from the Billing page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint=true, it discloses the required authorization scope, the mapping to the `ankra org billing wallet` CLI command, and a genuinely non-obvious semantic: an organisation never credited reads as absent, which means the free tier rather than an empty wallet. That last point prevents a common misinterpretation of a null/absent result, which annotations cannot convey.

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 resource identity, then the state fields, then the caveat about absence, then the access requirement. The first sentence is long due to its enumerated list but each clause carries distinct information; nothing is 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 input parameters, no output schema, and only a readOnlyHint annotation, the description carries the burden and does so by describing the returned fields in prose and pinning down the ambiguous absent-wallet case. An agent has everything needed to call it and interpret the result correctly.

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 no parameter meaning to add; the baseline for a parameterless tool applies. The description spends its words on response semantics instead, which is the right allocation.

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 (the organisation's prepaid credit wallet) and enumerates exactly what is reported: EUR net position, funding state (funded/grace/restricted/frozen), credit lots in spend order with expiry, and whether top-ups are open. An agent can distinguish this from get_billing_standing or get_usage without opening the schema.

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?

Gives the prerequisite (Requires billing.read), confirms it is read-only, and draws the boundary that credit is added from the Billing page, implying this tool is for inspection only. It does not explicitly name a sibling such as get_billing_standing as the alternative for different questions, so routing guidance is clear but not exhaustive.

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.