Skip to main content
Glama

Termin buchen

book_appointment

Bucht einen freien Termin (Zeit aus check_availability). Nur im Auftrag und mit den Angaben der Person, für die gebucht wird.

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": {
      "serviceId": "<serviceId>",
      "start": "<start>",
      "end": "<end>",
      "customerName": "<customerName>",
      "customerEmail": "<customerEmail>"
    },
    "name": "book_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnde, ISO 8601 mit Zeitzone
notesNoHinweis an den Betrieb (optional)
startYesBeginn, ISO 8601 mit Zeitzone
serviceIdYesKennung der Leistung
customerNameYesVor- und Nachname der Kundin bzw. des Kunden
customerEmailYesE-Mail für die Bestätigung
customerPhoneNoTelefonnummer (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations only mark it as a non-read-only operation, so the description usefully adds that the slot must be a free one obtained from check_availability and that third-party booking is the intended mode. It does not disclose what happens on a race/conflict, whether the call is idempotent, or what confirmation is produced, which matters for a mutation with 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?

Two short sentences with no filler, and the key constraint (free slot from check_availability) is front-loaded in parentheses. Efficient, though the parenthetical placement slightly buries the workflow prerequisite.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 7-parameter mutation with five required fields and no output schema needs more than it gets: the description covers the precondition and consent constraint but says nothing about the result of a successful booking or its failure behavior. Adequate to start the call correctly, incomplete for interpreting the outcome.

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%, so every parameter is already documented, including the email's confirmation purpose. The description only adds that start/end must originate from check_availability and that the name/contact fields belong to the person booked for; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Bucht einen freien Termin') and ties it to the sibling check_availability as the source of the time, so an agent can tell it apart from pure availability checking. The sole gap is that differentiation is expressed as a data dependency rather than an explicit contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

States two concrete usage conditions: the slot must come from check_availability, and booking happens only on behalf of the person whose details are supplied. No exclusions or failure-case guidance (e.g. what to do if the slot is gone) are given, but the prerequisites are clear.

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.

Resources