Skip to main content
Glama

Read a member and their open balances

member_get
Read-onlyIdempotent

Read one flat member's profile and every unsettled debt with other members, including amount, currency, and who owes whom, to check open balances before updating the member or moving them out.

Instructions

Read one member (id, name, active) plus openBalances: every unsettled debt between them and each other member, with member_id, name, amount_cents, currency and direction owes (this member still owes the other) or owed (the other owes them). Use it before member_update to see what money would be left open on a move-out. For all members at once use members_list, for what others owe you use balances_get, for debts between all members dashboard_get. Read-only; unknown ids give member_not_found.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "member_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the member, from members_list.
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. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / id / description
      Added value: +"Id of the member, from members_list."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Although annotations already state read-only and idempotent, the description adds substantial behavioral detail beyond them. It documents the return payload, including openBalances fields and the owes/owed direction semantics, and states that unknown ids return member_not_found.

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?

The description is front-loaded with the core action and return shape, then follows with usage and alternatives. It is dense but largely earns its length because there is no output schema, though the openBalances field enumeration makes the first sentence quite long.

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?

The tool has no output schema, so the description appropriately explains the returned fields and direction semantics. It also covers error behavior and alternatives, making it complete enough for an agent to call the tool correctly.

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 100%, so both id and wgCode are already well documented in the schema. The description does not add parameter-specific semantics beyond what the schema provides, so the baseline score of 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: "Read one member (id, name, active) plus openBalances". It clearly distinguishes this from sibling tools by naming members_list, balances_get, and dashboard_get as alternatives with different scopes.

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?

Gives explicit when-to-use guidance: "Use it before member_update to see what money would be left open on a move-out." It also routes the agent to alternatives for all members, what others owe you, and all-member debts.

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