Dollea Beauty Coworking

Eigene Zusatzverfügbarkeit anlegen

coworking_staff_create_special_day

Idempotent

Für den verbundenen Mitarbeiter einen besonderen verfügbaren Tag anlegen. Start und Ende müssen am selben lokalen Tag liegen.

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": {
      "start_at": "<start_at>",
      "end_at": "<end_at>",
      "submission_key": "<submission_key>"
    },
    "name": "coworking_staff_create_special_day"
  }
}

Input Schema

Name	Required	Description	Default
`end_at`	Yes	Ende der eigenen Verfügbarkeit oder Sperrzeit als ISO-Datum mit Zeitzonenoffset.
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de
`start_at`	Yes	Konkreter Terminbeginn als ISO-Datum mit Zeitzonenoffset. Relative Zeiten zuerst anhand der mitgelieferten Münchner Ortszeit auflösen.
`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.5/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral constraint (start and end must fall on the same local day), which is real value beyond the structured fields, but it omits any auth or side-effect context.

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?

Two short sentences, zero padding, and the core action is front-loaded ahead of the constraint. It is appropriately sized for the operation.

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, full parameter coverage, and annotations carrying the safety profile, the description is nearly complete. Only the sibling-routing distinction from create_block/create_special_day lifecycle is left unstated.

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 four parameters are documented in the schema itself. The description only reinforces the same-local-day relationship between start_at and end_at, adding no syntax or format detail beyond what the schema provides; 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?

States a specific verb (anlegen) and resource (besonderer verfügbarer Tag) scoped to the connected employee (verbundener Mitarbeiter). An agent can distinguish this from coworking_staff_create_block, but the description never explicitly contrasts the two sibling operations.

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 through the tool's framing as adding availability for the connected staff member. No explicit when-to-use vs coworking_staff_create_block or when-not guidance is given; the same-local-day rule is a constraint rather than routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dollea Beauty Coworking 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?