Dollea Cosmetics Salon

Aktuelle Salonaktion abrufen

salon_get_campaign

Read-onlyIdempotent

Die aktuell im Hero veröffentlichte Salonaktion einschließlich Code, Kundenkreis und Gültigkeit abrufen. Ein angezeigter Code bestätigt noch keine persönliche Rabattberechtigung.

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_get_campaign"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de

Output Schema

Name	Required	Description	Default
`business`	Yes
`campaign`	Yes
`language`	Yes
`timezone`	Yes
`local_date`	Yes
`hero_highlight`	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 declare the read-only, idempotent, non-destructive, closed-world profile, so the safety burden is covered. The description adds genuinely new behavioral context beyond the annotations: only the campaign currently published in the Hero is returned, and a displayed code does not by itself confirm personal discount eligibility — an important interpretation constraint.

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?

Two sentences, zero padding, and the purpose is front-loaded before the eligibility caveat. Every clause carries information the agent needs.

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 annotations covering safety and an output schema covering return structure, the description only needs to convey scope and meaning, which it does via the Hero-placement scope and the discount-eligibility caveat. Minor gaps remain: it does not say what happens when no campaign is published or what 'Hero' refers to for a non-visual caller.

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?

There is a single optional parameter (language) with 100% schema description coverage including the enum, so the schema already does the work. The description adds no additional meaning about language behavior, which matches the baseline 3 for high-coverage 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?

The description names a specific verb (abrufen) and resource (die aktuell im Hero veröffentlichte Salonaktion) and even enumerates the returned contents (Code, Kundenkreis, Gültigkeit), so the agent knows exactly what comes back. It does not, however, explicitly contrast itself with the promo/pricing siblings such as salon_get_price or salon_get_quote, which is what a 5 would require.

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 can infer it should call this when it needs the currently displayed campaign and its code. There is no explicit when-to-use statement and no routing away from the related siblings (salon_get_price, salon_get_quote), so the guidance is adequate but thin.

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?