Skip to main content
Glama

getecoback-raumklima

luftbefeuchter_stellplatz_risiko

Read-only

Aufstellung des vorhandenen Befeuchters bei Spritzwasser, kalter Wand oder Dampf prüfen — Check for a safer humidifier location from observed placement conditions.

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": {
      "steam": "<steam>",
      "reachable_by_children": "<reachable_by_children>",
      "moisture_deposits": "<moisture_deposits>",
      "manual_location_ok": "<manual_location_ok>"
    },
    "name": "luftbefeuchter_stellplatz_risiko"
  }
}

Input Schema

NameRequiredDescriptionDefault
steamYesGeräteanleitung nennt heißen Dampf oder heiße Geräteteile?
moisture_depositsYesSichtbarer Niederschlag an Wand, Möbel oder Oberfläche in der Nähe?
manual_location_okYesStandort entspricht allen dokumentierten Modellabständen und Untergrundvorgaben?
reachable_by_childrenYesGerät, Kabel oder Dampfbereich im Betrieb erreichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world assessment. The description adds that the evaluation is driven by observed placement conditions, but it never says what the verdict looks like (risk level, pass/fail, recommended relocation) 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.

Conciseness4/5

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

A single compact sentence with the hazard conditions front-loaded before the English gloss. The bilingual duplication costs a little space but aids disambiguation; nothing else is wasted.

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?

For a four-required-boolean assessment tool with no output schema, the description should convey what the check returns and how inputs are weighed. It conveys the trigger conditions adequately but leaves the result shape and any safety-critical escalation behavior unspecified.

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 every boolean is documented in German in the schema itself; the baseline is 3. The description echoes two of the four inputs (steam/Dampf, moisture/Spritzwasser-nasse Wand) but adds no interpretation of how combinations map to a risk outcome, and never mentions the reachable_by_children or manual_location_ok dimensions.

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 (prüfen/check) and a specific resource (Aufstellung des vorhandenen Befeuchters), and scopes it to three concrete hazard triggers: Spritzwasser, kalte Wand, Dampf. It is clearly distinguishable from the outdoor-unit sibling klima_aussenteil_stellplatz_check, but it does not name any sibling explicitly.

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 rather than stated: an agent can infer this applies when observed placement conditions raise a concern, and the phrase 'safer humidifier location' hints at the goal. There is no explicit when-not guidance, no mention of prerequisites, and no named alternative tool for related humidifier tasks such as neustart or pflege.

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