Skip to main content
Glama

getecoback-climate-weather

luftbefeuchter_zweistufen_tank_restmenge

Read-only

Für zwei schon vermessene Stufen bestimmen, welche nach dem Wechsel noch aus dem vorhandenen Wasser läuft. — Budget measured water for two humidifier modes without projecting a room effect.

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": {
      "wasser_ml": "<wasser_ml>",
      "erster_bedarf_ml": "<erster_bedarf_ml>",
      "zweiter_bedarf_je_stunde_ml": "<zweiter_bedarf_je_stunde_ml>",
      "zweite_stufe_min": "<zweite_stufe_min>",
      "wechsel_bestaetigt": "<wechsel_bestaetigt>"
    },
    "name": "luftbefeuchter_zweistufen_tank_restmenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
wasser_mlYesNutzbares Wasser oberhalb der dokumentierten Mindestgrenze vor dem ersten Abschnitt.
erster_bedarf_mlYesBei vergleichbaren Bedingungen gemessene Menge im ersten Abschnitt.
zweite_stufe_minYesGeplante Minuten in der zweiten Stufe.
wechsel_bestaetigtYesIst der Wechsel mit dieser Restfüllung beim konkreten Modell nach Anleitung möglich?
zweiter_bedarf_je_stunde_mlYesBeobachtete Nutzung pro Stunde in der zweiten Stufe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 one genuine behavioral constraint — it does not project a room effect, i.e. it is a pure water-budget computation — but says nothing about what is returned (remaining ml, remaining minutes, a verdict) or how the wechsel_bestaetigt gate changes the outcome.

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?

Two short sentences with no filler, and the core operation is stated first. The second sentence is a partially redundant English gloss whose clause 'without projecting a room effect' is the only non-duplicated content, so it is close to wasted space but not harmful.

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

Completeness2/5

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

There is no output schema, so the description is the only place the result could be characterized — yet it never says what the tool produces. For a five-required-parameter read-only calculation, the agent knows neither the return shape nor how the boolean confirmation parameter affects the result.

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% with five required, individually documented numeric/boolean parameters, so the schema does the heavy lifting. The description only hints that the two stage inputs must be 'schon vermessen' (previously measured); it adds no units, ranges, or interpretation beyond the schema, so the baseline 3 applies.

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 German sentence conveys a specific-enough intent — compute, for two already-measured humidifier stages, how much of the available water still carries the run after the switch — but the verb is the generic 'bestimmen' and the object ('welche ... noch aus dem vorhandenen Wasser läuft') is grammatically vague. The appended English fragment ('Budget measured water for two humidifier modes without projecting a room effect') re-states the idea less precisely rather than sharpening it, so an agent cannot cleanly distinguish this from siblings such as befeuchter_tank_laufzeit or entfeuchter_tank_leerintervall.

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?

No when-to-use guidance and no named alternative among the many sibling tools. The only scoping hint is the negative 'without projecting a room effect', which implies a boundary but never says which tool handles the room-effect case or when this budget calculation is the right call.

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