Skip to main content
Glama

List members

members_list
Read-onlyIdempotent

Lists every flat member, including moved-out ones, with IDs, active and admin status plus pagination, so you can look up member IDs for other tools or identify who is active. Read-only.

Instructions

List every member of the flat, including moved-out ones, with id, name, color, active and viewerIsAdmin, plus pagination total/limit/offset. Use it to look up member ids for other tools (payer, assignee, split debtor) or to find who is active; filter on active yourself. For one member and their open balances call member_get, for what others owe you call balances_get. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, default and maximum 500. Moved-out members stay listed, so the roster only grows.
offsetNoNumber of members to skip, ordered by join date. Use with pagination.total.
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. Changed3 schema fields changedv0.3.0
    • removedInput schema / properties / limit / default
      Removed value: -100
    • changedInput schema / properties / limit / description
      Previous value: -"Page size. Moved-out members stay listed, so the roster only grows."New value: +"Page size, default and maximum 500. Moved-out members stay listed, so the roster only grows."
    • removedInput schema / properties / offset / default
      Removed value: -0
  2. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / limit / description
      Added value: +"Page size. Moved-out members stay listed, so the roster only grows."
    • addedInput schema / properties / offset / description
      Added value: +"Number of members to skip, ordered by join date. Use with pagination.total."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds genuinely new behavior: the roster is append-only because moved-out members stay listed, and there is no active filter — the caller must filter client-side. It does not describe ordering (join date appears only in the schema) or failure modes such as an invalid wgCode, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with what is returned before the routing guidance; every clause carries information except the trailing "Read-only," which merely repeats readOnlyHint=true. No padding or hedging otherwise.

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 output schema, the description correctly enumerates the returned fields and pagination shape, and it covers the zero-required-parameter case by noting wgCode can be omitted for single-flat accounts only indirectly via the schema. For a simple list tool it gives an agent everything needed to call and interpret it.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by clarifying that 'active' is a returned field rather than a query parameter, which prevents a plausible misuse not obvious from the schema. It restates the pagination triple (total/limit/offset) but leaves limit/offset semantics to the schema, which already documents defaults, maximum, and ordering.

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?

The first sentence names a specific verb and resource ("List every member of the flat") and immediately states the scope that distinguishes it: it includes moved-out members and returns id, name, color, active, viewerIsAdmin. Sibling tools member_get and balances_get are named as the alternatives for different questions, so an agent can route 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 Guidelines5/5

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

It gives concrete positive uses ("look up member ids for other tools (payer, assignee, split debtor)", "find who is active") plus an explicit operational instruction ("filter on active yourself") and names two alternatives with the conditions that select them (member_get for one member and balances; balances_get for what others owe).

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