Skip to main content
Glama

getecoback-climate-weather

entfeuchter_tank_leerintervall

Read-only

Zeit bis zum vollen Entfeuchtertank aus eigener Messung abschätzen — Estimate tank-emptying interval from collected water and time.

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": {
      "free_capacity_l": "<free_capacity_l>",
      "collected_l": "<collected_l>",
      "measured_h": "<measured_h>"
    },
    "name": "entfeuchter_tank_leerintervall"
  }
}

Input Schema

NameRequiredDescriptionDefault
measured_hYesVergleichszeitraum in Stunden.
collected_lYesIm Vergleichszeitraum tatsächlich gesammelte Liter.
free_capacity_lYesNoch freies nutzbares Tankvolumen in Litern bis zur Abschaltung.

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 safety and scope are covered. The description adds that this is a pure estimate computed from measured inputs rather than a sensor read, but says nothing about the assumptions behind the extrapolation (linear rate) or the unit/format of the returned interval.

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, front-loaded clauses — the German statement followed by its English equivalent — with no filler. The bilingual duplication costs a little space but aids comprehension, and the core purpose is stated first.

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-required-parameter calculation tool with no output schema, the description should at least indicate what the returned value is (hours until full? days? a range?). It states the goal in prose but leaves the result format and the linear-rate assumption unstated, which is a meaningful gap for an agent deciding whether to call it.

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 each of the three parameters carrying its own German description including units and bounds, so the schema does the heavy lifting. The description adds no further detail on how the inputs combine (e.g. that free capacity divided by the measured rate yields the interval), 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 specific computation: estimating the time until the dehumidifier tank is full, derived from the user's own measurements. The phrase 'aus eigener Messung' hints that this is measurement-based as opposed to a lookup or check tool, but it never names the sibling (e.g. entfeuchter_leerer_tank_check) it should be chosen over.

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: it says the estimate comes from collected water and elapsed time, which suggests the needed preconditions, but there is no explicit when-to-use, when-not-to-use, or pointer to a similar sibling tool. An agent must infer that this is the extrapolation tool rather than the threshold-check 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