Skip to main content
Glama

Read open balances

balances_get
Read-onlyIdempotent

Lists what other flat members currently owe you, one entry per debtor and currency, to identify who to remind about outstanding payments.

Instructions

Lists what other members currently owe the caller (creditor view), one entry per debtor and currency with debtor_id, debtor_name, amount_cents (cents), currency and oldest_age_days. Read only. Use it to find who to remind with reminder_send; the result is empty when nobody owes the caller. It does not show what the caller owes or debts between other members (use dashboard_get), and gives no settlement detail (use settlement_preview).

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

Input Schema

NameRequiredDescriptionDefault
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description's "Read only" is redundant but harmless. It adds genuinely new behavioral facts the annotations cannot convey: the result is empty when nobody owes the caller, and units (amount_cents in cents, oldest_age_days). No pagination or auth notes, which is the only gap.

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-loads purpose, then return shape, then behavioral note, then sibling routing — a well-ordered structure with no filler sentences. Minor waste in restating "Read only" already covered by annotations and in the dense inline field list, but every sentence still carries information.

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?

There is no output schema, and the description compensates by enumerating the returned fields and the empty-result condition. Combined with explicit scope boundaries and sibling routing, an agent has everything needed to decide to call it and interpret the response.

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?

Only one optional parameter (wgCode) and schema description coverage is 100%, including the pattern and the "leave it out when the account belongs to one flat" guidance. The description adds nothing about it, but the schema already carries the meaning, so the baseline 3 applies.

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 ("Lists what other members currently owe the caller") plus the exact granularity ("one entry per debtor and currency") and the field set returned. The creditor-view framing distinguishes it from a general dashboard or settlement view without the agent needing to open a schema.

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

Usage Guidelines5/5

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

Names the downstream consumer ("Use it to find who to remind with reminder_send") and gives explicit exclusions with named alternatives: what the caller owes or debts between other members goes to dashboard_get, settlement detail goes to settlement_preview. Both when-to-use and when-not-to-use are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.