Skip to main content
Glama

getecoback-raumklima

Kellerentfeuchter: Gefälle, Pumpe oder Tank?

entfeuchter_ablaufcheck
Read-onlyIdempotent

Prüft für Kellerentfeuchter, ob der Schlauch mit Gefälle ablaufen kann oder eine passende Pumpe bzw. Tankbetrieb zu prüfen ist. Nennt die Quelle zum genauen Modell. — Check a German basement dehumidifier’s hose route, pump or tank options and cite evidence for the exact model.

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": {
      "drain": "<drain>"
    },
    "name": "entfeuchter_ablaufcheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
drainYesGesamter Schlauchweg: downhill = durchgehend abwärts, level_or_uphill = waagerechtes oder ansteigendes Teilstück, no_drain = kein Zielablauf, unknown = ungeklärt.
modelNoOptionaler exakter Katalogschlüssel. Bei abweichender oder unbekannter Modellvariante unknown verwenden.
moistureNoBisheriger Befund: unbekannt, unauffällig, anhaltend hoch oder sichtbarer Schaden. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds genuinely new behavioral context: the result is evidence-cited to a specific model rather than a generic recommendation. It stops short of describing the verdict's output shape, but with annotations in place that is a minor gap.

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?

The content is front-loaded and each sentence carries the scope, the two outcome branches, and the citation promise. The full German/English duplication is deliberate bilingualism but is redundant for a single reader, which keeps it from a 5.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only advisory tool with three fully documented enum parameters and no output schema, the description supplies what an agent needs: what is evaluated, the decision branches, and that model-specific evidence is cited. Nothing required for correct invocation is missing.

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 coverage is 100% and all three parameters carry enum descriptions, so the schema does the heavy lifting. The description mentions Gefälle, Pumpe and Tankbetrieb, which loosely echoes the drain and moisture dimensions, but adds no syntax, default, or interaction detail beyond the schema.

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

Purpose5/5

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

The description names a concrete verb ("Prüft") and a narrowly scoped resource: the hose drainage path of a basement dehumidifier. It also states the two possible verdicts (downhill drain vs. pump/tank) and that it names a source for the exact model, which clearly separates it from the sizing and selection siblings.

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 domain (Kellerentfeuchter hose routing) implies the usage context, but there is no explicit statement of when to prefer this tool over e.g. geraet_wahl or when it is not applicable. The only routing hint is that it names the source for the exact model, which is implicit rather than a stated alternative.

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