Skip to main content
Glama

Read absences

absences_list
Read-onlyIdempotent

Lists current and upcoming absences of flat members, ordered by start date. Use it to see who is away and to get absence IDs for removal.

Instructions

List the absences of flat members that are running or still ahead (an absence stays listed until its end date has passed, counted in Berlin time), ordered by start. Use it to see who is away; use events_list for flat calendar events, absence_create to record a new absence and absence_delete to remove one. Each entry has id, memberId, memberName, startDate, endDate (ISO 8601) and reason (text or null); the id is what absence_delete needs.

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

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.6/5.0
Behavior5/5

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

Beyond the read-only/idempotent hints, it discloses the non-obvious listing lifetime rule (an absence stays listed until its end date has passed), the timezone used to evaluate that boundary (Berlin time), and the sort order. It also states the exact return fields, which matters because there is no output schema.

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-loaded with the core behavior, then alternatives, then the return shape — a sensible order with no filler. The sentence enumerating return fields is justified only because no output schema exists, but it makes the paragraph denser than strictly needed.

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?

Given no output schema and a single optional parameter, the description covers everything an agent needs: what is listed, the boundary rule and timezone, ordering, and the identity of each field including the id required by absence_delete. Nothing required to invoke it correctly 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 description coverage is 100%, and the single wgCode parameter is fully documented in the schema (share code from wg_list, omittable for single-flat accounts). The description adds nothing about that parameter, so this sits at the baseline for schema-complete tools.

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 ("List the absences of flat members") plus the exact scope: absences that are running or still ahead, ordered by start. It explicitly separates itself from events_list, absence_create and absence_delete, so an agent can pick it without opening any 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 a direct when-to-use statement ("Use it to see who is away") and names the sibling that covers the adjacent need ("use events_list for flat calendar events"), plus routing to absence_create/absence_delete for mutation. Both inclusion and exclusion guidance are present.

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