Dollea Beauty Coworking

Coworking-Arbeitsplätze finden

coworking_search_workspaces

Read-onlyIdempotent

Beauty-Coworking-Ressourcen in München nach Tätigkeit, Ausstattung, Personenzahl und Datum finden. Gruppen teilen die Belegung mit ihren Einzelplätzen. Persönliche Mietpreise erfordern eine autorisierte Preisprüfung.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximale Anzahl zurückgegebener Ergebnisse innerhalb der veröffentlichten Grenze.
`query`	No	Kurze Suchbegriffe zur gewünschten Behandlung, Tätigkeit oder Ausstattung.
`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
`groups_only`	No	Nur kombinierte Gruppen-Workspaces anzeigen.
`min_persons`	No	Benötigte Mindestkapazität des Workspaces.
`available_on`	No	Nur Ressourcen mit tatsächlich freier Kapazität an diesem lokalen Datum anzeigen.
`equipment_ids`	No	Alle erforderlichen Ausstattungskennungen müssen am Workspace vorhanden sein.
`supported_uses`	No	Gewünschte Tätigkeiten als strukturierte Kennungen, beispielsweise manicure, lashes oder cosmetics.

Output Schema

Name	Required	Description	Default
`items`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes
`business`	Yes
`language`	Yes
`timezone`	Yes
`local_date`	Yes
`next_offset`	Yes
`contract_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful disclosure that personal rental prices require an authorized price check, but says nothing about pagination beyond what the schema states or about result ordering.

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, front-loaded with the core purpose. The middle and last sentences add context without waste, though the price-check sentence could be clearer about what action an agent should take.

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 cover safety. However, as a search tool among many siblings with overlapping date-based functionality, the description omits routing guidance (e.g., when to prefer coworking_find_dates), leaving an agent to guess between alternatives.

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 nine parameters in detail. The description adds only a high-level summary of the filter categories and does not add syntax, format, or interaction details beyond the schema.

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 (finden) and resource (Beauty-Coworking-Ressourcen) with scoping dimensions (Tätigkeit, Ausstattung, Personenzahl, Datum). It does not differentiate itself from the closest sibling coworking_find_dates, which also handles date-based discovery, so the sibling boundary is left to inference.

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?

Usage is implied through the filter dimensions, and the comment about personal rental prices suggests when a different tool (price check) may be needed, but there is no explicit statement of when to use this search vs. coworking_find_dates or coworking_get_price.

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?