Dollea Beauty Coworking

Coworking-Buchung vorbereiten

coworking_prepare_booking

Ein persönliches Mietangebot für ausgewählte oder wiederkehrende Tage erstellen. Konflikte werden ausdrücklich ausgewiesen. Die Vorbereitung bucht nichts. Monatspauschalen und zusätzliche Tagesgebühren getrennt darstellen.

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": {
      "workspace_id": "<workspace_id>",
      "dates": "<dates>"
    },
    "name": "coworking_prepare_booking"
  }
}

Input Schema

Name	Required	Description	Default
`dates`	Yes	Explizite lokale Miettage im Format JJJJ-MM-TT. Der Server prüft jeden Tag und kennzeichnet Konflikte.
`notes`	No	Optionaler Hinweis des buchenden Nutzers, maximal 2000 Zeichen.
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de
`recurrence`	No	Optionale wöchentliche oder monatliche Wiederholung der ausdrücklich gewählten Tage bis zum lokalen Enddatum.
`workspace_id`	Yes	Aktuelle numerische Workspace-Kennung aus coworking_search_workspaces.

Output Schema

Name	Required	Description	Default
`offer`	Yes
`status`	Yes
`business`	Yes
`language`	Yes
`quote_id`	Yes
`timezone`	Yes
`expires_at`	Yes
`local_date`	Yes
`contract_version`	Yes
`requires_confirmation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=false, openWorldHint=false, and idempotentHint=false, but the description adds real behavioral context: conflicts are explicitly flagged, the call does not create a booking despite readOnlyHint=false, and monthly flat rates are shown separately from daily fees. This clarifies that the tool produces a computed offer rather than committing state, which is exactly the kind of nuance annotations cannot convey.

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?

Four short, front-loaded sentences covering purpose, conflict handling, the non-booking guarantee, and pricing output. Each sentence carries weight and none is padded, though the pricing sentence is somewhat tangential to tool selection.

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?

An output schema exists, so return values need not be explained. For a 5-parameter, nested-object mutation-adjacent tool the description covers the key agent concerns: it computes rather than books, flags conflicts, and separates pricing components. It only lacks explicit routing to sibling tools, which keeps it short of a 5.

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 dates, recurrence, notes, language, and workspace_id in detail. The description only hints at 'ausgewählte oder wiederkehrende Tage' without adding format, constraint, or format-selection guidance beyond the schema, so the 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?

The description names a specific verb and resource: 'Ein persönliches Mietangebot ... erstellen' (create a personal rental offer for selected or recurring days). It implicitly separates itself from the booking-confirmation sibling by noting it does not book anything, but it never names an alternative tool, so sibling differentiation is only partial.

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?

'Die Vorbereitung bucht nichts' implies this is a pre-booking step that must precede coworking_confirm_booking, which gives a usable workflow hint. However, it never states when to choose this versus coworking_get_quote or coworking_find_dates, nor any explicit exclusions, so usage is inferred rather than directed.

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?