Dollea Cosmetics Salon

Salonangebot prüfen

salon_get_quote

Read-onlyIdempotent

Ein eigenes Salonangebot mit Kennung und Zugriffsschlüssel lesen. Aktuelle Änderungen werden als erneute Angebotsprüfung gekennzeichnet. Keine fremden Kontaktdaten werden offengelegt.

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

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.

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.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: that current changes surface as a renewed offer review, and that no third-party contact data is exposed — useful disclosure 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, no redundancy, with the core action stated first and the behavioral caveats after. Every sentence carries information.

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 no explanation, and the description covers access requirements, mutation/refresh semantics and a privacy guarantee. The only gap is the absence of routing guidance against the many sibling read tools.

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 quote_id, quote_token and language are already fully documented in the schema. The description's 'mit Kennung und Zugriffsschlüssel' merely restates two of them without adding format, validation or language-selection meaning, matching the baseline 3.

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 gives a specific verb ('lesen') and resource ('eigenes Salonangebot') plus the credentials required, which cleanly separates it from siblings like salon_get_booking, salon_get_price or salon_get_campaign. It does not explicitly name those siblings, so it falls short of a 5.

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 only implied: the agent infers it should call this when it holds a quote_id plus access key for its own prepared offer. There is no statement of when to prefer this over salon_get_booking or what to do if the key is missing, so it stays at the minimum-viable level.

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?