Dollea Cosmetics Salon

Salontermin verbindlich buchen

salon_confirm_booking

DestructiveIdempotent

Das zuvor geprüfte Salonangebot nach ausdrücklicher Zustimmung zu Preis und Bedingungen buchen. Der Server prüft Preis, Mitarbeiter und Verfügbarkeit erneut. Wiederholte Bestätigung gibt dieselbe Buchung zurück. Es werden Buchungsbestätigungen versendet.

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_cancellation": "<accept_cancellation>"
    },
    "name": "salon_confirm_booking"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de
`quote_id`	Yes	Kennung des zuvor vom Server vorbereiteten Buchungsangebots.
`quote_token`	Yes	Nur beim Erstellen ausgegebener Zugriffsschlüssel des Angebots. Nicht veröffentlichen oder aus fremden Daten ableiten.
`accept_terms`	No	Nur true senden, wenn der Nutzer die gezeigten Nutzungsbedingungen und den Angebotspreis bestätigt hat.
`accept_privacy`	Yes	Nur true senden, wenn der Nutzer den gezeigten Datenschutzbedingungen zugestimmt hat.
`accept_cancellation`	Yes	Nur true senden, wenn der Nutzer die gezeigten Stornierungsbedingungen bestätigt hat.
`confirm_partial_series`	No	Bei einer verkürzten Mietserie nur nach ausdrücklicher Zustimmung zu allen ausgelassenen Tagen true senden.

Output Schema

Name	Required	Description	Default
`status`	Yes
`booking`	Yes
`business`	Yes
`language`	Yes
`quote_id`	Yes
`timezone`	Yes
`local_date`	Yes
`contract_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructive, idempotent and openWorld hints; the description adds real context by noting the server re-validates price, staff and availability, and that booking confirmations are sent. The idempotency note ('Wiederholte Bestätigung gibt dieselbe Buchung zurück') largely restates the idempotentHint but clarifies the returned artifact, while the re-check and email details are genuinely new.

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?

Four short sentences, front-loaded with the action and its precondition, then behavioral facts. No filler or repetition; every sentence contributes.

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?

The tool is a destructive, idempotent mutation with a full output schema and complete annotation coverage. The description covers precondition, server-side re-validation, idempotency and confirmation emails, leaving little an agent needs to know before calling it.

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 every parameter, including the const-true consent booleans and the quote token. The description's mention of 'ausdrücklicher Zustimmung zu Preis und Bedingungen' loosely maps to the accept_* flags but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 – booking the previously prepared salon offer ('Das zuvor geprüfte Salonangebot ... buchen'). The phrase 'zuvor geprüfte' clearly ties it to the prepare step, distinguishing it from siblings like salon_prepare_booking and salon_get_quote.

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?

Explicitly names the precondition: booking happens only after explicit consent to price and conditions ('nach ausdrücklicher Zustimmung zu Preis und Bedingungen'). The 'zuvor geprüfte' phrasing implies the prior prepare step, but no sibling alternative is named by name and no when-not guidance is given.

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

All Dollea Cosmetics Salon tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?