Dollea Cosmetics Salon

Salonpreis prüfen

salon_get_price

Read-onlyIdempotent

Den aktuellen Preis für einen konkreten Salontermin berechnen. Für einen Promocode werden echte E-Mail-Adresse und Telefonnummer benötigt. Die Prüfung reserviert keinen Termin und verbraucht keine Einlösung.

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>"
    },
    "name": "salon_get_price"
  }
}

Input Schema

Name	Required	Description	Default
`customer`	No	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
`slot`	Yes
`total`	Yes
`pricing`	Yes
`business`	Yes
`discount`	Yes
`language`	Yes
`subtotal`	Yes
`timezone`	Yes
`local_date`	Yes
`contract_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior: the check does not reserve a slot and does not burn the redemption, and promo eligibility is validated server-side — meaningful side-effect context beyond the annotations.

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?

Three short sentences, each earning its place: the core action, the promo prerequisite, and the no-side-effect guarantee. The purpose is front-loaded and there is no filler.

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?

With an output schema present, return values need not be described, and the annotations carry the safety profile. What remains — the promo prerequisite and the fact that nothing is reserved or consumed — is exactly the non-obvious information an agent needs before calling this tool.

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 thoroughly, including the e-mail/phone requirement for promo checks and the staff-preference behavior. The description's promo-code note largely restates what the schema already says, so it sits at the high-coverage baseline rather than adding new meaning.

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 specific verb and resource: calculates the current price for a concrete salon appointment. That is concrete and unambiguous, but it offers no differentiation from the sibling salon_get_quote, whose purpose appears adjacent, leaving the agent to guess which of the two to pick.

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?

Gives clear usage context: a promo code requires a real e-mail address and phone number, establishing the prerequisite for that scenario. The sentence that the check neither reserves an appointment nor consumes a redemption implicitly distinguishes it from the booking siblings, though no alternative tool is named explicitly.

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?