Dollea Beauty Coworking

Persönlichen Coworking-Preis prüfen

coworking_get_price

Read-onlyIdempotent

Den persönlichen Mietpreis für konkrete Tage prüfen. Aktuelle Wochenkonditionen, Account-Freigabe und Monatspauschalen werden berücksichtigt. Eine Monatspauschale ist keine kostenlose Miete.

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_get_price"
  }
}

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.
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de
`workspace_id`	Yes	Aktuelle numerische Workspace-Kennung aus coworking_search_workspaces.

Output Schema

Name	Required	Description	Default
`dates`	Yes
`lines`	Yes
`total`	Yes
`business`	Yes
`language`	Yes
`timezone`	Yes
`local_date`	Yes
`billing_mode`	Yes
`workspace_id`	Yes
`partial_series`	Yes
`rejected_dates`	Yes
`contract_version`	Yes
`monthly_agreement`	Yes
`existing_price_changes`	Yes
`additional_booking_total`	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 establish a safe, idempotent, non-destructive read, so the description is not obligated to cover safety. It adds genuine behavioral context: pricing accounts for weekly conditions, account approval status, and monthly flat rates, and it flags the non-obvious 'a monthly flat rate is not free rent' caveat.

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?

Three short sentences with the action front-loaded and no filler. The final caveat sentence is slightly tangential but earns its place by correcting a plausible misconception about monthly flat rates.

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?

With an output schema present, return values need not be described, and annotations carry the safety profile. The description covers what the price depends on and its scope, leaving only sibling differentiation unaddressed.

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 workspace_id, dates, and language fully. The description only echoes the 'concrete days' concept and adds no syntax, format, or constraint detail 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?

States a specific verb (prüfen/check) and resource (persönlicher Mietpreis) scoped to concrete days. It is clear on its own, but it never distinguishes itself from the sibling coworking_get_quote, whose purpose overlaps heavily with a price retrieval tool.

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 'für konkrete Tage prüfen' implies the tool is used when concrete dated pricing is needed, which is usable context. However, there is no explicit when-to-use versus coworking_get_quote, coworking_prepare_booking, or coworking_find_dates, and no exclusions.

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?