Dollea Cosmetics Salon

Salonstornierung anfragen

salon_request_cancellation

DestructiveIdempotent

Eine Stornierung des eigenen Salontermins anfragen. Die Antwort enthält den tatsächlichen Entscheidungsstatus. Anfrage und genehmigte Stornierung nicht gleichsetzen.

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": {
      "booking_token": "<booking_token>",
      "submission_key": "<submission_key>"
    },
    "name": "salon_request_cancellation"
  }
}

Input Schema

Name	Required	Description	Default
`reason`	No	Vom Nutzer bereitgestellter Hinweis zur gewünschten Änderung oder Stornierung.
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de
`booking_token`	Yes	Privater Schlüssel des eigenen Salontermins aus der Buchungsbestätigung. Er berechtigt nicht zum Zugriff auf andere Termine.
`submission_key`	Yes	Neue UUID für eine neue Anfrage; bei Wiederholungen exakt dieselbe UUID verwenden.

Output Schema

Name	Required	Description	Default
`business`	Yes
`language`	Yes
`timezone`	Yes
`local_date`	Yes
`contract_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already flag destructive=true, idempotent=true and readOnly=false, so the mutation profile is known. The description adds genuinely new context beyond that: the call only files a request and the response carries the real decision status, so a request must not be treated as an approved cancellation.

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, front-loaded sentences with no filler. The core action comes first, then the result semantics, then the misinterpretation warning — every sentence carries weight.

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?

An output schema exists, so return values need not be enumerated, and the destructive/idempotent hints are covered by annotations. The one thing an agent could still want — that submissions are repeat-safe via submission_key — lives in the schema, leaving the description complete enough for this flow.

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 booking_token, submission_key, reason and language are already documented in the schema. The description adds no syntax, format or constraint detail beyond it, which is the baseline 3 for fully covered schemas.

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 ('Eine Stornierung des eigenen Salontermins anfragen') and scopes it to the user's own appointment. It implicitly separates itself from salon_request_change, but never names that sibling to make the routing explicit.

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 context is implied by 'des eigenen Salontermins', but there is no explicit when-to-use/when-not or pointer to alternatives such as salon_request_change for modifications rather than cancellations. The two closing sentences address interpretation of the result, not tool selection.

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?