Dollea Cosmetics Salon

Salonbuchung vorbereiten

salon_prepare_booking

Ein kurzlebiges Angebot für die gewählten Salonleistungen, Kontaktdaten und den konkreten Termin erstellen. Dies bucht noch keinen Termin und sendet keine E-Mail. Vor Bestätigung die vollständige Preisübersicht und Bedingungen zeigen.

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": {
      "service_ids": "<service_ids>",
      "start_at": "<start_at>",
      "customer": "<customer>"
    },
    "name": "salon_prepare_booking"
  }
}

Input Schema

Name	Required	Description	Default
`customer`	Yes	Vom Kunden bereitgestellte Kontaktdaten. Für eine persönliche Aktionsprüfung müssen E-Mail und Telefonnummer vorhanden sein.
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de
`staff_id`	No	Optionaler ausdrücklich gewünschter Mitarbeiter. Eine ungeeignete oder nicht verfügbare Präferenz wird nicht ersetzt.
`start_at`	Yes	Konkreter Terminbeginn als ISO-Datum mit Zeitzonenoffset. Relative Zeiten zuerst anhand der mitgelieferten Münchner Ortszeit auflösen.
`promo_code`	No	Vom Kunden gewünschter oder aktuell veröffentlichter Promocode. Seine Berechtigung wird serverseitig geprüft.
`service_ids`	Yes	Aktuelle numerische Leistungskennungen aus salon_search_services. Mehrere Leistungen werden als zusammenhängender Besuch geprüft.

Output Schema

Name	Required	Description	Default
`offer`	Yes
`status`	Yes
`business`	Yes
`language`	Yes
`quote_id`	Yes
`timezone`	Yes
`expires_at`	Yes
`local_date`	Yes
`contract_version`	Yes
`requires_confirmation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive write; the description adds that the result is short-lived and that no booking or email occurs, which materially clarifies side-effect scope beyond the annotations. It does not mention expiry duration or how the offer is later consumed by salon_confirm_booking.

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?

Three compact sentences with no redundancy, and the core scoping plus the booking/email negation are front-loaded. The final sentence is a workflow instruction rather than a description of the tool itself, slightly diluting focus.

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 a rich schema, an output schema, and annotations already covering the safety profile, the description supplies the essential scope and side-effect framing. Only minor gaps remain (offer lifetime, relationship to the quote/price siblings).

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% and every parameter already carries a German description (customer, language, staff_id, start_at, promo_code, service_ids), so the schema does the heavy lifting. The prose adds no additional parameter semantics, making the baseline 3 correct.

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?

States a concrete verb (erstellen) and resource (kurzlebiges Angebot) scoped to selected services, contact data, and a specific appointment, and explicitly negates booking, which cleanly separates it from salon_confirm_booking. It does not address the potential overlap with salon_get_quote/salon_get_price, so full sibling differentiation is missing.

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 says what this tool does NOT do ("bucht noch keinen Termin und sendet keine E-Mail") and prescribes a next step before confirmation (show full price overview and terms). No guidance, however, on when to prefer it over salon_get_quote or salon_get_price.

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?