Dollea Beauty Coworking

Eigene Coworking-Buchungen lesen

coworking_list_bookings

Read-onlyIdempotent

Ausschließlich Mietbuchungen des aktuell verbundenen Kontos mit Status und persönlichen Tagespreisen lesen.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "coworking_list_bookings"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximale Anzahl zurückgegebener Ergebnisse innerhalb der veröffentlichten Grenze.
`offset`	No	Ergebnisposition für die nächste Seite; next_offset aus der vorherigen Antwort verwenden.
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de

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.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is fully covered. The description adds a useful filtering detail (exclusively rental bookings) and mentions returned status and personal daily prices, but it does not disclose pagination behavior or other runtime traits beyond the schema.

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?

The description is a single front-loaded sentence with no filler. Every clause contributes to defining scope and output content.

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 read-only list tool with rich annotations, a complete input schema, and an output schema, the description is largely sufficient. It states the account scope and the type of bookings returned, though it could have clarified its relationship to sibling tools like coworking_get_booking.

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?

The input schema has 100% description coverage for limit, offset, and language, including a default and enum constraints. The description adds no parameter-level detail, so the baseline of 3 is appropriate when the schema does the heavy lifting.

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 gives a precise verb ('lesen') and resource ('Mietbuchungen'), scoped to the currently connected account. It does not explicitly differentiate from siblings such as coworking_get_booking or coworking_list_invoices, so it falls short of a 5 despite being clear.

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 'Ausschließlich Mietbuchungen des aktuell verbundenen Kontos' implies usage is restricted to the connected account's rental bookings, giving a scoping hint. However, it does not say when to choose this tool over alternatives like coworking_get_booking or coworking_list_invoices, leaving the agent to infer.

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?