Skip to main content
Glama

Record an absence

absence_create

Records a flat member's absence for a date range, such as a holiday, so others can see when they are away.

Instructions

Record that a flat member is away for a date range, for example a holiday. Use it for a person being away; use event_create for a calendar entry that concerns the whole flat. Members can record their own absence; recording one for another member needs a flat admin, otherwise 403 not_owner. The memberId must belong to an active member of this flat. An endDate before startDate fails with date_range_invalid. An absence that overlaps another absence of the same member (by Berlin calendar day) fails with 409 absence_overlaps_existing. Returns the created absence with its id.

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": {
      "memberId": "<memberId>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "absence_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional free-text reason, for example "Holiday". Omit or send null for none.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
endDateYesLast day of the absence, inclusive, as ISO 8601 datetime with offset, not before startDate. Only the Berlin calendar day counts.
memberIdYesId of the absent member, from members_list or wg_overview. Use your own member id unless you are a flat admin.
startDateYesFirst day of the absence as ISO 8601 datetime with offset, for example 2026-12-24T00:00:00+01:00. Only the Berlin calendar day counts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / endDate / description
      Added value: +"Last day of the absence, inclusive, as ISO 8601 datetime with offset, not before startDate. Only the Berlin calendar day counts."
    • addedInput schema / properties / memberId / description
      Added value: +"Id of the absent member, from members_list or wg_overview. Use your own member id unless you are a flat admin."
    • addedInput schema / properties / reason / description
      Added value: +"Optional free-text reason, for example \"Holiday\". Omit or send null for none."
    • addedInput schema / properties / startDate / description
      Added value: +"First day of the absence as ISO 8601 datetime with offset, for example 2026-12-24T00:00:00+01:00. Only the Berlin calendar day counts."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by naming concrete failure modes with status codes: 403 not_owner for recording another member's absence without admin, date_range_invalid for an inverted range, and 409 absence_overlaps_existing for overlapping absences by Berlin calendar day. It also states the successful return value (the created absence with its id), which the annotations do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five tight sentences with no filler: purpose and sibling split are front-loaded, then authorization, then validation and conflict rules, then the return value. Every sentence carries distinct, actionable information.

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 5-parameter mutation tool with no output schema, the description covers purpose, alternative, authorization, validation failures, conflict behavior, and the shape of the response. Nothing an agent needs 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns above that by adding constraints not in the schema, namely that memberId must belong to an active member of this flat and that only the Berlin calendar day of the datetimes matters for overlap. It does not restate reason or wgCode, but those are fully documented in the 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 specific verb and resource ("Record that a flat member is away for a date range") and immediately contrasts it with the sibling event_create for whole-flat calendar entries. An agent can distinguish this from event_create without inspecting either 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 routing guidance ("use it for a person being away; use event_create for a calendar entry that concerns the whole flat") plus the permission condition for recording for another member. Both the when-to-use and the when-not/alternative cases are covered.

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