Skip to main content
Glama

German Real Estate Depreciation & Restnutzungsdauer

List free AfAMax initial-call appointment slots

get_available_appointments
Read-only

Lists open slots for a free, non-binding 30-minute initial phone call with the AfAMax team (Erstgespräch), on weekdays in the Europe/Berlin time zone, grouped by day.

Each day lists a sample spread across the day (maxSlotsPerDay, default 8) and its freeSlotCount; for a specific time, call again for that day with days: 1 and maxSlotsPerDay: 32. Show the user the day and localTime; to book one, pass its startDateTime unchanged to book_appointment. Slots are live and can be taken at any time, so re-check rather than reusing an old list. The response attribution links to the contact page, where the user can also book directly.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many calendar days to look ahead (1-21, default 7). / Anzahl Tage.
fromNoISO 8601 date-time to start looking from. Defaults to now. / Frühester Zeitpunkt.
localeNoLanguage of the link handed back and the response labels. Match the user's language (most users are German-speaking).de
maxSlotsPerDayNoHow many slots to list per day (1-32, default 8), spread evenly across the day. When the user wants a specific time, call again for that day with `days: 1` and `maxSlotsPerDay: 32`.

Output Schema

NameRequiredDescriptionDefault
daysYes
metaYes
timeZoneYes
requestIdYes
attributionYes
descriptionYes
appointmentTypeYes
durationMinutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, not idempotent), and the description adds substantial context on top: slots are live and can disappear at any time, results are sampled and spread across the day with a freeSlotCount, and the response carries an attribution link. The volatility warning directly explains why idempotentHint=false matters in practice.

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 purpose, then workflow, then the booking handoff — a logical order with no filler. It is dense and runs long-ish for a list tool, but nearly every clause carries operative 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?

Even though an output schema exists, the description usefully previews the shape (grouped by day, sample spread, freeSlotCount) and covers time zone, liveness, and booking handoff. Nothing needed to call 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 coverage is 100%, so parameters are already documented; the description nonetheless adds workflow meaning beyond the schema — the retry pattern for a specific time (days:1 with maxSlotsPerDay:32), the sampling behavior of maxSlotsPerDay, and the instruction to match locale to the user's language.

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 open slots') plus the exact scope: free, non-binding 30-minute initial phone call, weekdays, Europe/Berlin, grouped by day. An agent can distinguish it immediately from book_appointment or the pricing/calculation siblings.

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?

Explicitly routes to alternatives: pass startDateTime unchanged to book_appointment to book, call again with days:1 and maxSlotsPerDay:32 to drill into a specific day, and re-check rather than reusing an old list. Both the when-to-use and the sibling handoff are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.