Dollea Beauty Coworking

Eigene Sperrzeit ändern

coworking_staff_update_block

DestructiveIdempotent

Eine eigene Sperrzeit mit vollständigen neuen Zeitgrenzen ändern. Fremde Mitarbeiter können nicht ausgewählt werden.

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

Input Schema

Name	Required	Description	Default
`end_at`	Yes	Ende der eigenen Verfügbarkeit oder Sperrzeit als ISO-Datum mit Zeitzonenoffset.
`reason`	No	Vom Nutzer bereitgestellter Hinweis zur gewünschten Änderung oder Stornierung.
`block_id`	Yes	Kennung einer eigenen Sperrzeit aus coworking_staff_availability.
`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.
`service_category_id`	No	Optionale eigene Leistungskategorie; ohne Kategorie gilt die Sperre für alle eigenen Leistungen.

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 destructiveHint=true, idempotentHint=true and readOnlyHint=false, lowering the bar. The description adds one genuinely useful behavioral fact beyond the annotations: the change is a full replacement of time boundaries ('vollständigen neuen Zeitgrenzen'), not a merge. It stops there, saying nothing about what happens to omitted optional fields or any side effects.

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 core action front-loaded and the access constraint second. No filler, though the second sentence is a usage constraint rather than deepening the purpose.

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?

A rich schema (100% coverage), full annotations, and an output schema mean the description need not explain parameters or return values. For an idempotent destructive update it covers the action, the replacement semantics and the ownership constraint, leaving only minor gaps around omitted-field behavior.

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 the schema already documents all seven parameters including submission_key idempotency semantics and service_category_id fallback behavior. The description only implies the start_at/end_at pair via 'vollständigen neuen Zeitgrenzen' and adds nothing beyond the schema, so 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+resource (Sperrzeit ändern) with a clear scope limiter ('eine eigene Sperrzeit') that distinguishes it from the create/delete block siblings by verb alone. It is clear, but does not explicitly name or contrast with siblings such as coworking_staff_create_block or coworking_staff_delete_block.

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?

The description gives a real constraint ('Fremde Mitarbeiter können nicht ausgewählt werden') which hints at who may use it and on which records, but there is no explicit when-to-use this vs. create_block/delete_block guidance and no stated prerequisites (that block_id must come from coworking_staff_availability) beyond what the schema provides.

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?