Dollea Beauty Coworking

Freie Coworking-Tage finden

coworking_find_dates

Read-onlyIdempotent

Freie Miettage eines Workspaces prüfen. Die Belegung von Gruppen und enthaltenen Arbeitsplätzen wird gemeinsam berücksichtigt. Es werden keine Daten anderer Mieter offengelegt.

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>",
      "from_date": "<from_date>"
    },
    "name": "coworking_find_dates"
  }
}

Input Schema

Name	Required	Description	Default
`to_date`	No	Letzter lokaler Kalendertag des begrenzten Suchzeitraums, einschließlich dieses Tages.
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de
`from_date`	Yes	Erster lokaler Kalendertag in München, im Format JJJJ-MM-TT.
`workspace_id`	Yes	Aktuelle numerische Workspace-Kennung aus coworking_search_workspaces.

Output Schema

Name	Required	Description	Default
`dates`	Yes
`business`	Yes
`language`	Yes
`timezone`	Yes
`local_date`	Yes
`workspace_id`	Yes
`available_dates`	Yes
`contract_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine context beyond them: availability is computed jointly across groups and included workstations, and no other tenants' data is exposed – useful behavioral facts an agent cannot infer from 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?

Three short sentences with the core purpose front-loaded, followed by the occupancy-computation note and the privacy guarantee. No filler; every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, and annotations carry the safety profile. However, for a tool sitting among many booking/availability siblings, the absence of any routing guidance leaves a meaningful gap.

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 four parameters, including the date formats, the language enum, and the workspace_id provenance. The description adds no parameter-level detail, which is acceptable given full schema coverage – baseline 3.

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 – checking a workspace's free rental days ('Freie Miettage eines Workspaces prüfen'). It is clear what the tool returns, though it does not explicitly distinguish itself from availability-adjacent siblings like coworking_staff_availability or coworking_search_workspaces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus the many siblings that also deal with dates or workspaces (e.g. coworking_search_workspaces, coworking_staff_availability). No prerequisites, exclusions, or sequencing guidance are given.

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?