Dollea Beauty Coworking

Coworking-Stornierung anfragen

coworking_request_cancellation

DestructiveIdempotent

Eine Stornierung der eigenen Mietbuchung anfragen. Nur eine dauerhafte Anfrage wird angelegt und benachrichtigt; Wiederholungen geben dieselbe Anfrage zurück.

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": {
      "booking_id": "<booking_id>",
      "submission_key": "<submission_key>",
      "reason": "<reason>"
    },
    "name": "coworking_request_cancellation"
  }
}

Input Schema

Name	Required	Description	Default
`reason`	Yes	Vom Nutzer bereitgestellter Hinweis zur gewünschten Änderung oder Stornierung.
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de
`booking_id`	Yes	Kennung einer eigenen Mietbuchung aus coworking_list_bookings.
`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.8/5.0

Behavior4/5

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

With destructiveHint and idempotentHint already set, the description still adds real value: it explains that only one persistent request is created and notified, and that repeats return the same request. This concretely ties the idempotency annotation to the submission_key mechanism, though it does not detail the destructive consequence (e.g. whether the booking ends immediately or stays pending).

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 tight sentences with the mutation and its idempotency consequence front-loaded. Every clause earns its place with zero padding.

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?

Return values are covered by the existing output schema, parameters by full schema coverage, and safety/idempotency by annotations plus the description's own statement. The only minor gap is the absence of explicit routing against coworking_request_change.

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 booking_id, submission_key, reason and language are all self-documented. The description adds no syntax or format detail beyond the schema, so the baseline of 3 is appropriate.

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: 'eine Stornierung der eigenen Mietbuchung anfragen' (request cancellation of one's own booking). The action and target are unambiguous and distinct from a generic change request. It stops short of naming a sibling, but an agent can still tell what it does.

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 phrase 'eigenen Mietbuchung' scopes usage to the caller's own bookings, which is a useful implied condition. However, it never states when to prefer this over the sibling coworking_request_change, nor any exclusions or prerequisites. Usage is implied rather than guided.

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?