Skip to main content
Glama

getecoback-raumklima

befeuchter_tank_laufzeit

Read-only

Befeuchter-Nachfüllzeit aus nutzbarem Tank und eigener Verbrauchsrate bestimmen — Estimate humidifier refill interval from usable capacity and observed water use.

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": {
      "usable_tank_ml": "<usable_tank_ml>",
      "observed_use_ml": "<observed_use_ml>",
      "observed_h": "<observed_h>"
    },
    "name": "befeuchter_tank_laufzeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
observed_hYesDauer der Verbrauchsmessung in Stunden.
usable_tank_mlYesNutzbares Füllvolumen in ml bis zur vorgesehenen Nachfüllgrenze.
observed_use_mlYesIm gleichen Modus verbrauchte Wassermenge in ml.

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 agent knows this is a side-effect-free closed calculation. The description adds that the result is an estimate derived from two inputs, but says nothing about the output unit (hours vs. days), rounding, or linearity assumptions; with annotations covering the safety profile, that is adequate rather than rich.

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 purpose front-loaded and zero filler. The German and English halves are largely duplicative, but the bilingual phrasing plausibly serves the mixed-language domain, so the redundancy is mild rather than wasteful.

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 three-input pure calculator with full schema coverage and no output schema, the definition covers what the tool is but not what it returns – no indication that the answer is an interval in hours, nor any note on how out-of-range or inconsistent inputs are handled. It is callable as written, but an agent cannot predict the shape or semantics of 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% and each parameter carries bounds and a German description, so the schema already does the heavy lifting. The description merely restates the two inputs ('usable capacity and observed water use') without adding units, constraints, or the same-mode requirement that the schema spells out – baseline 3 is appropriate.

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 and resource: estimate/bestimmen the refill interval (Nachfüllzeit) from tank capacity and observed consumption. That is precise enough to distinguish the humidifier (Befeuchter) case from the dehumidifier siblings, though it never explicitly names entfeuchter_tank_leerintervall as the counterpart, so the differentiation is implicit in the wording rather than stated.

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 only implied: an agent can infer it applies when you have usable capacity plus an observed-consumption measurement. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. the dehumidifier counterpart), and no note that the measurement must be taken in the same operating mode or that the result is an extrapolation.

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