Skip to main content
Glama

List your flats

wg_list
Read-onlyIdempotent

List all flats the signed-in account belongs to, including id, name, share code, and memberId, so you can choose the wgCode required by flat-scoped tools.

Instructions

Lists every flat the signed-in account is an active member of, each with id, name, share code (code) and your memberId in it. Use it first when the account belongs to several flats, then pass the chosen code as wgCode to every flat-scoped tool; wg_list and wg_create work on the account and take no wgCode. To see the members and details of one flat, call wg_overview instead. 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": "wg_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description's trailing "Read-only" is largely redundant. What it does add beyond annotations is the return shape and the account-scoped vs flat-scoped distinction, which is genuinely useful behavioral context. It does not mention empty results or ordering, a minor 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?

Three sentences, front-loaded with the purpose and return fields, then the workflow, then the alternative. Every sentence carries information, though the closing "Read-only." duplicates the readOnlyHint annotation and could be dropped.

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, so the description must describe returns, and it does so precisely (id, name, code, memberId). Combined with the wgCode handoff guidance and the wg_overview pointer, an agent has everything needed to call this correctly on the first try.

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?

The tool takes zero parameters, so the baseline is 4. The description usefully reinforces this by stating that wg_list and wg_create work on the account and take no wgCode, preventing an agent from inventing a flat argument.

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 every flat the signed-in account is an active member of") and enumerates the returned fields (id, name, share code, memberId). It explicitly distinguishes itself from wg_overview and wg_create, so an agent can pick it 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?

Gives explicit when-to-use guidance ("Use it first when the account belongs to several flats"), the downstream action (pass the chosen code as wgCode to flat-scoped tools), and a named alternative for a different need (wg_overview for one flat's members and details). It also clarifies which tools take no wgCode, removing a likely invocation error.

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