Skip to main content
Glama

Coworking verbindlich buchen

coworking_confirm_booking
DestructiveIdempotent

Das eigene geprüfte Coworking-Angebot verbindlich buchen. Teilweise verfügbare Serien müssen ausdrücklich bestätigt werden. Preise und Belegung werden erneut geprüft. Wiederholungen erzeugen keine weiteren Miettage oder Bestätigungen.

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": {
      "quote_id": "<quote_id>",
      "quote_token": "<quote_token>",
      "accept_privacy": "<accept_privacy>",
      "accept_terms": "<accept_terms>"
    },
    "name": "coworking_confirm_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoGewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.de
quote_idYesKennung des zuvor vom Server vorbereiteten Buchungsangebots.
quote_tokenYesNur beim Erstellen ausgegebener Zugriffsschlüssel des Angebots. Nicht veröffentlichen oder aus fremden Daten ableiten.
accept_termsYesNur true senden, wenn der Nutzer die gezeigten Nutzungsbedingungen und den Angebotspreis bestätigt hat.
accept_privacyYesNur true senden, wenn der Nutzer den gezeigten Datenschutzbedingungen zugestimmt hat.
accept_cancellationNoNur true senden, wenn der Nutzer die gezeigten Stornierungsbedingungen bestätigt hat.
confirm_partial_seriesNoBei einer verkürzten Mietserie nur nach ausdrücklicher Zustimmung zu allen ausgelassenen Tagen true senden.

Output Schema

NameRequiredDescriptionDefault
statusYes
bookingYes
businessYes
languageYes
quote_idYes
timezoneYes
local_dateYes
contract_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description goes beyond them by explaining the concrete semantics: prices and occupancy are re-validated at commit time, and repeated calls do not create additional rental days or confirmations. It still omits what auth/consent preconditions are strictly enforced and how binding/complex cancellation afterward is.

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?

Four short sentences, front-loaded with the core action, then the partial-series caveat, then the re-check and idempotency notes. Each sentence carries distinct information, though the 'verbindlich buchen' framing is slightly restated by the title.

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

Completeness4/5

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

With an output schema present, return values need not be explained, and annotations cover the mutation profile. The description supplies the key preconditions (verified quote, explicit partial-series consent) and the idempotency semantics, making it sufficient for correct invocation, though it could say more about the aftermath (how to cancel/change).

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 the schema already documents all seven parameters, including quote_token secrecy and the const:true accept flags. The description adds only marginal meaning, hinting at the confirm_partial_series parameter via the 'teilweise verfügbare Serien' sentence. Baseline 3 is appropriate.

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?

The description states a specific verb and resource: 'Das eigene geprüfte Coworking-Angebot verbindlich buchen'. This clearly positions it as the binding commit step that follows a previously prepared offer, distinct from coworking_prepare_booking. It does not, however, name the sibling tools by name, so an agent must infer the ordering.

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

Usage Guidelines3/5

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

Usage is implied through the precondition of an existing 'geprüftes Angebot' and the note that partially available series require explicit confirmation (linking to confirm_partial_series). There is no explicit statement of when to call this versus read-only siblings like coworking_get_booking or coworking_list_bookings, and no exclusion guidance.

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