Skip to main content
Glama

getecoback-climate-weather

luftbefeuchter_raumwechsel_wasseralter_nachweis

Read-only

Bestimme beim Weitergeben eines Befeuchters das maximal belegte Alter des Tankwassers — Track the oldest documented tank water through a humidifier handoff

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": {
      "volle_neubefuellung_min": "<volle_neubefuellung_min>",
      "nachfuellen_min": "<nachfuellen_min>",
      "uebergabe_min": "<uebergabe_min>",
      "tankvorgang_vollstaendig_belegt": "<tankvorgang_vollstaendig_belegt>"
    },
    "name": "luftbefeuchter_raumwechsel_wasseralter_nachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
uebergabe_minYesMinute der Geräteübergabe im gleichen Protokoll
nachfuellen_minYesMinute des letzten belegten bloßen Nachfüllens; wie Wasserwechselminute setzen, wenn keines erfolgte
volle_neubefuellung_minYesMinute des letzten belegten vollständigen Wasserwechsels
tankvorgang_vollstaendig_belegtYesBefüllen und Nachfüllen sind für dieselbe Tankeinheit nachvollziehbar

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description is consistent with a pure computation. It adds the useful framing that the result is the oldest *documented* water age across a handoff, but says nothing about what happens when documentation is incomplete or what form the returned age takes.

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 line with the operative verb front-loaded and no filler. The German/English duplication is redundant but short enough not to impede comprehension.

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-parameter derived-value tool with no output schema, the description should at least signal the shape of the result (e.g. an age in minutes) and how incomplete documentation is reported. It leaves that to inference, though the rich schema coverage keeps the gap from being severe.

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 four parameters are individually documented in the schema (including the fallback rule for nachfuellen_min). The description adds no meaning beyond that — it does not explain how the three minute values combine into the reported age — so the baseline 3 applies.

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 concrete action ("Bestimme"/"Track") and a concrete resource ("das maximal belegte Alter des Tankwassers") scoped to a humidifier handoff, so an agent can tell it computes a derived value rather than mutating state. It does not contrast itself with the many neighbouring luftbefeuchter_* tools (e.g. nachfuellen_kleine_portionen, zweistufen_tank_restmenge), so it stops short of full sibling differentiation.

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?

"Beim Weitergeben eines Befeuchters" gives an implied trigger condition for calling the tool, which is real but minimal guidance. There is no statement of when not to use it, no prerequisites (e.g. that minutes must come from the same log), and no named alternative among the sibling tools.

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