Skip to main content
Glama

getecoback-raumklima

entfeuchter_gemeinsamer_ablauf_wegzeiten_absprache

Read-only

Ein dokumentiertes festes Ablauf-Setup mit einer gleichzeitig gewünschten Durchgangsfreigabe abgleichen — Flag a room-use collision when the approved drainage setup must stay in place.

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": {
      "ablauf_blockiert_weg": "<ablauf_blockiert_weg>",
      "weg_gebraucht": "<weg_gebraucht>",
      "ausweichweg_bestaetigt": "<ausweichweg_bestaetigt>",
      "tankmodus_bestaetigt": "<tankmodus_bestaetigt>"
    },
    "name": "entfeuchter_gemeinsamer_ablauf_wegzeiten_absprache"
  }
}

Input Schema

NameRequiredDescriptionDefault
weg_gebrauchtYesEine andere Person hat denselben Weg während dieser Zeit fest eingeplant.
ablauf_blockiert_wegYesDie bereits dokumentierte feste Aufstellung hält den betreffenden Weg während der Nutzung belegt.
tankmodus_bestaetigtYesTankbetrieb am anderen vorgesehenen Platz ist laut Anleitung und vor Ort bereits geklärt.
ausweichweg_bestaetigtYesEin geeigneter anderer Weg wurde bereits vor Ort geprüft und vereinbart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the operation is a comparison that flags a collision rather than a mutation, which is useful, but it does not describe what the flag looks like or what happens on the non-collision case, and there is no output schema to fill that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, which is good, but the German/English mix and the em-dash construction make it harder to parse than a plain statement. The core purpose is not front-loaded before the ambiguity.

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?

All four parameters are required and fully documented in the schema, and the readOnly annotation covers the risk profile. However, the tool's essential logic — which combination of the four booleans constitutes a collision and what the agent should do with the result — is never stated and cannot be recovered from the schema, so the description stops short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every one of the four booleans carries a clear German explanation, so the baseline is 3. The description goes slightly beyond by framing the two pairs (documented setup vs. requested passage) as the terms being reconciled, which helps the agent see how the parameters relate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an action ("abgleichen"/"Flag a room-use collision") and a resource domain (a documented fixed drainage setup vs. a requested passage clearance), so the intent is roughly graspable. But it is an abstract, bilingual phrasing that never states plainly what the tool returns or how it differs from the many sibling entfeuchter_* checks, leaving the agent to infer the operation.

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-to-use guidance and no reference to any alternative among the siblings. The clause "when the approved drainage setup must stay in place" hints at a trigger condition but does not function as routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources