Dollea Beauty Coworking

Eigene Arbeitszeiten lesen

coworking_staff_availability

Read-onlyIdempotent

Die eigenen Wochenzeiten, besonderen Tage und Sperrzeiten lesen. Kundentermine und fremde Mitarbeiterdaten werden nicht ausgegeben.

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

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.

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

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value beyond that by disclosing a data-visibility boundary: customer appointments and other employees' data are deliberately not returned. No pagination or response-shape notes, but the output schema covers returns.

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 compact sentences, the resource list front-loaded and the scoping caveat immediately after. Zero filler, no restatement of the title.

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 tool the description plus annotations plus a full-coverage schema and an output schema cover everything needed to call it correctly. The only gap is the absence of any routing guidance toward or away from sibling tools.

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%, with format, default, enum values and a precise description of the inclusive date range already documented per parameter. The description adds no parameter-level detail, 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?

Specifies a concrete verb ("lesen") and the resources read: own weekly hours, special days, block times. The possessive "eigenen" plus the explicit exclusion of customer/other-employee data frames the scope against the write-oriented staff siblings (create/update/delete block/special day). It never names an alternative tool, so differentiation is implied rather than stated.

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 when-to-use or when-not guidance and no alternative tool is named. The agent can infer it is the read counterpart to the staff write tools, but nothing in the text tells it when this tool is the right choice over, e.g., coworking_list_bookings or coworking_get_account.

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?