Skip to main content
Glama

Get expense group balances

well_get_expense_group_balances
Read-only

Get who owes whom in one shared-expense group: each member's balance and the fewest transfers that settle the group. It writes nothing.

balances gives each member's balance as a signed decimal string in the group's currency: above zero the group owes the member, below zero the member owes the group. The balances sum to zero. transfers lists the fewest payments that bring every balance to zero, each with from_person_id, to_person_id, their names and amount. An empty transfers means the group is settled. Well computes these figures from every expense and repayment of the group: state them as returned.

Read outcome: read, or refused with reason group_not_found (no such group in this workspace) or too_many_rows (the group is too large to compute in one read).

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.
expense_group_idYesThe group, a row of `well_list_expense_groups`.

Output Schema

NameRequiredDescriptionDefault
errorNo
groupNo
reasonNo
outcomeNo
successYes
balancesNo
transfersNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / group / properties / closed_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / group / properties / closed_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive, but the description adds what the annotations cannot: the sign convention for `balance`, the zero-sum invariant, that an empty `transfers` means settled, that the figures are derived from all expenses and repayments and must be 'stated as returned', and the two concrete refusal modes (`group_not_found`, `too_many_rows`). That is real behavioral context beyond structured fields.

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 the purpose, then explains outputs, then error handling, then workspace behavior — a sensible progression with no filler sections. A few clauses are mildly redundant with the schema (e.g., repeating the workspace_id rule) but nothing is wasted at length.

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?

For a read tool with an output schema, 4 params and a non-trivial derived computation, the description covers invocation preconditions, output semantics, invariants, and failure outcomes. Nothing an agent needs to call this correctly and interpret the result is missing.

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 coverage is 100% and every parameter — including workspace_id, conversation_id and workspace_scope — is documented in the schema itself. The description restates the workspace_id rule but adds nothing about conversation_id or workspace_scope, so it hovers at the baseline for a fully documented 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?

Opens with a concrete verb and resource plus scope: 'Get who owes whom in one shared-expense group', and immediately names the two outputs (balances, minimal transfers). An agent can distinguish this from well_list_expense_groups or well_get_expense_transfer_qr without opening 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 Guidelines4/5

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

Gives a clear routing rule for workspace selection (single-workspace token -> call directly; multi-workspace token -> pass workspace_id, no guessing) and names well_list_expense_groups as the source of the group ID. It stops short of explicitly contrasting with adjacent siblings such as the transfer-QR tool or the create-settlement tool, so it's clear context without full alternative coverage.

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.

Resources