Skip to main content
Glama

Wallet balance

get_wallet_balance
Read-onlyIdempotent

Selected country balance and ledger. Omit workspace_id for the original default wallet.

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
workspace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so safety is covered. The description adds that the result is country-scoped and includes a ledger, plus default-wallet fallback behavior, but says nothing about return shape or pagination.

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 short sentences with no wasted words, and the default-wallet rule is stated directly. The opening 'Selected country balance and ledger' is slightly opaque but compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single optional-parameter read tool with rich annotations and no output schema, the description is minimally sufficient. It still leaves 'selected country' undefined and does not indicate what the ledger contains, which matters for an agent deciding whether this tool answers its question.

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 description coverage is 0%, and the description explains the default-wallet behavior when workspace_id is omitted. However, it does not explain what supplying a workspace_id selects or whether it must correspond to an existing country workspace.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'balance and ledger' for the 'selected country', which conveys the resource better than the name alone, but 'selected country' is undefined and there is no explicit verb. It does not differentiate the tool from siblings like list_country_workspaces or check_account_status.

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

Usage Guidelines2/5

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

The only guidance is a parameter hint: omit workspace_id for the original default wallet. There is no statement of when to use this tool versus alternatives, nor any prerequisites or exclusions.

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.