Skip to main content
Glama

getecoback-climate-weather

entfeuchter_leerer_tank_check

Read-only

Leeren Tank vor einem Ersatzkauf eingrenzen — Troubleshoot an empty dehumidifier tank using the actual setting, temperature and drain mode.

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": {
      "current_rh_pct": "<current_rh_pct>",
      "setpoint_rh_pct": "<setpoint_rh_pct>",
      "room_c": "<room_c>",
      "documented_minimum_c": "<documented_minimum_c>",
      "hose_in_use": "<hose_in_use>"
    },
    "name": "entfeuchter_leerer_tank_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
room_cYesLufttemperatur innen in °C.
hose_in_useYesAblaufschlauch statt Tankbetrieb angeschlossen?
current_rh_pctYesRelative Feuchte der Raumluft in Prozent.
setpoint_rh_pctYesRelative Feuchte der Raumluft in Prozent.
documented_minimum_cYesMindesttemperatur laut Anleitung für den gewählten Modus.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that the description only says the check uses 'the actual setting, temperature and drain mode' — it never says what the diagnostic concludes, how hose_in_use changes the verdict, or what form the answer takes. For a read-only tool with no output schema, this is a meaningful 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 front-loaded sentence with no wasted clauses, and the scoping intent precedes the mechanics. The clipped German phrasing slightly hurts readability but nothing is padded.

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?

Five required numeric/boolean inputs and no output schema mean the description should convey how the inputs combine into a conclusion; it does not. Safety behavior is covered by annotations, so the remaining gap is the reasoning/return expectation rather than permissions.

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 five parameters carry German descriptions, so the schema does the heavy lifting. The description loosely maps three concepts (setting, temperature, drain mode) onto setpoint_rh_pct/room_c, documented_minimum_c and hose_in_use, but adds no interpretation such as comparing room_c against documented_minimum_c or which setpoint takes precedence.

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 diagnostic action ('Troubleshoot an empty dehumidifier tank') and the inputs driving it (setting, temperature, drain mode), plus a scoping intent ('vor einem Ersatzkauf eingrenzen'). It does not differentiate from near-neighbours such as entfeuchter_tank_leerintervall or entfeuchter_ablaufcheck, and the German opening ('Leeren Tank ... eingrenzen') is grammatically awkward, but the core purpose is identifiable.

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 by 'vor einem Ersatzkauf eingrenzen' — invoke this before buying a replacement part to narrow down the cause. There is no explicit when-not condition and no pointer to the closest alternatives (tank interval, drain hose check), leaving routing to inference.

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