Dollea Cosmetics Salon

Salonleistungen finden

salon_search_services

Read-onlyIdempotent

Aktuelle Salonleistungen in München nach Behandlung, Mitarbeiter, Dauer, Richtpreis und Datum finden. Ergebnisse enthalten Live-Kennungen und erfüllte Anforderungen. Preise werden vor der Buchung erneut berechnet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "salon_search_services"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximale Anzahl zurückgegebener Ergebnisse innerhalb der veröffentlichten Grenze.
`query`	No	Kurze Suchbegriffe zur gewünschten Behandlung, Tätigkeit oder Ausstattung.
`offset`	No	Ergebnisposition für die nächste Seite; next_offset aus der vorherigen Antwort verwenden.
`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.
`available_on`	No	Nur Ressourcen mit tatsächlich freier Kapazität an diesem lokalen Datum anzeigen.
`category_slug`	No	Optionaler unveränderter Kategorie-Slug aus dem aktuellen Katalog.
`max_price_cents`	No	Höchster Richtpreis in EUR-Cent vor einer persönlichen Aktionsprüfung. Der endgültige Preis wird separat berechnet.
`max_duration_minutes`	No	Maximale Behandlungsdauer in Minuten; Anzeigeformate sind kein Eingabeformat.

Output Schema

Name	Required	Description	Default
`items`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes
`business`	Yes
`campaign`	Yes
`language`	Yes
`timezone`	Yes
`local_date`	Yes
`next_offset`	Yes
`contract_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description adds real value: it discloses the geographic scoping to München, that results carry live identifiers and fulfilled requirements, and that prices are recalculated before booking — a meaningful caveat for a pricing-related search. It does not, however, describe pagination behavior beyond what the schema already states.

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 tight sentences, front-loaded with the core action and resource, with no filler. The pricing caveat and result-content note are each one clause and earn their place.

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 full output schema present, return values need not be explained, and the annotations carry the safety profile. The description is complete enough to call the tool correctly, missing only explicit routing guidance against sibling 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 all nine parameters are already documented in the schema (staff_id, available_on, max_price_cents, etc.). The description's mention of treatment, staff, duration, price and date maps directly onto those existing schema fields without adding syntax or format detail, so the baseline 3 applies.

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 states a specific verb+resource ('Aktuelle Salonleistungen in München ... finden') and enumerates the filter axes, making the tool's function immediately clear. It implicitly contrasts with siblings like salon_find_slots (slots, not services) and salon_get_price, but never names an alternative to sharpen the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance is given, and no alternatives are named despite several overlapping siblings (salon_find_slots, salon_get_price, salon_get_quote). The agent must infer the search use case from the filter list alone.

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?