Skip to main content
Glama

getecoback-climate-weather

luftbefeuchter_neustart_pflege

Read-only

Wiederinbetriebnahme nach einer Nutzungsunterbrechung planen — Check a humidifier before reuse after standing water or storage.

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": {
      "tank": "<tank>",
      "visible_damage": "<visible_damage>",
      "prescribed_care_done": "<prescribed_care_done>",
      "fresh_approved_water": "<fresh_approved_water>"
    },
    "name": "luftbefeuchter_neustart_pflege"
  }
}

Input Schema

NameRequiredDescriptionDefault
tankYesZustand nach der Pause.
visible_damageYesSchaden, Leck oder Materialveränderung festgestellt?
fresh_approved_waterYesVorgeschriebenes frisches Wasser für dieses Modell verfügbar?
prescribed_care_doneYesVorgeschriebene Start- und Pflegeschritte vollständig erledigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The read-only and closed-world annotations establish that this is a safe, non-external assessment, while the description adds the reuse-after-downtime safety context. It does not explain whether the tool returns a checklist, readiness decision, or restart plan, nor how standing water or visible damage affects that result.

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 definition is compact, front-loaded, and free of procedural filler. The bilingual wording is somewhat redundant, and 'planen' versus 'Check' leaves a minor ambiguity between producing a plan and performing an assessment.

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?

The schema and annotations provide most invocation details, making the description adequate for tool selection. Because there is no output schema, however, the description should clarify the expected result and basic safety-gating behavior, especially when damage, incomplete care, or unsuitable water is reported.

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%, and the tank enum plus the three boolean inputs are already documented, so the baseline is 3. The description reinforces the standing-water scenario but adds no further interpretation of the individual inputs or how they are combined.

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 identifies a specific resource and task: checking or planning a humidifier's recommissioning after an interruption, standing water, or storage. It does not explicitly distinguish this restart check from sibling humidifier care, water-approval, or wick-maintenance tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage trigger is clear: use before reuse following a usage interruption, standing water, or storage. There are no exclusions or instructions for routing damage findings, routine model care, or water-approval questions to another tool.

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