Dollea Beauty Coworking

Eigene Zusatzverfügbarkeit entfernen

coworking_staff_delete_special_day

DestructiveIdempotent

Einen eigenen besonderen verfügbaren Tag entfernen. Andere Mitarbeiterprofile bleiben außerhalb dieser Berechtigung.

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": {
      "special_day_id": "<special_day_id>",
      "submission_key": "<submission_key>"
    },
    "name": "coworking_staff_delete_special_day"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de
`special_day_id`	Yes	Kennung eines eigenen besonderen Tages aus coworking_staff_availability.
`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 readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile and repeat-submission behavior are covered elsewhere. The description adds the scoping boundary ('Other staff profiles remain outside this permission'), which is useful context beyond the annotations, but does not explain what exactly gets removed or the effect on existing bookings.

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 with the action front-loaded and the scope constraint second. Efficient, with no wasted wording; it could be slightly more informative given the destructive nature but is not padded.

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?

For a destructive delete with annotations covering safety and idempotency, an output schema, and fully documented parameters, the description supplies the essential scope boundary. It is adequate, though noting the destructive/irreversible effect explicitly would make it more complete.

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 coverage is 100%, so all three parameters including the language enum and the special_day_id reference are already documented. The description adds no syntax, format, or UUID-reuse detail beyond what the schema already 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 and resource: removing one's own special available day. Clearly distinguishes from the sibling coworking_staff_delete_block and from coworking_staff_create_special_day via the 'eigenen' scope, though it doesn't explicitly name the alternative tools.

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 implied by the name and the reference to a day from coworking_staff_availability, but there is no explicit when-to-use guidance, no mention of when not to use it, and no named alternative such as delete_block.

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?