Skip to main content
Glama

getecoback-raumklima

entfeuchter_tankleerungen_zeitbilanz

Read-only

Kondensat eines Beobachtungszeitraums aus Tankbeständen und protokollierten Leerungen rekonstruieren — Recover collected condensate from start and end stock plus documented emptying.

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": {
      "tank_anfang_l": "<tank_anfang_l>",
      "tank_ende_l": "<tank_ende_l>",
      "entleert_l": "<entleert_l>",
      "leerungen_vollstaendig": "<leerungen_vollstaendig>"
    },
    "name": "entfeuchter_tankleerungen_zeitbilanz"
  }
}

Input Schema

NameRequiredDescriptionDefault
entleert_lYesGemessene Summe aller zwischendurch ausgeleerten Mengen in Litern.
tank_ende_lYesKondensat im Behälter zum letzten Messzeitpunkt.
tank_anfang_lYesKondensat im Behälter zum ersten Messzeitpunkt.
leerungen_vollstaendigYesSind alle Leerungen erfasst und andere Zu- oder Abflüsse ausgeschlossen?

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 and the description only needs to add behavior. It adds that this is a reconstruction/balancing computation over a period, but says nothing about what happens when leerungen_vollstaendig is false — whether the call errors, returns a qualified result, or proceeds silently — which is the single most consequential behavioral detail for a required boolean flag.

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 that states the reconstructed quantity before its inputs, with zero padding. The German/English duplication is mildly redundant but aids bilingual parsing rather than obscuring the core statement.

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 computation tool with no output schema, the description covers inputs but leaves the return value unstated (presumably liters of collected condensate, but the agent must guess) and does not explain the effect of the leerungen_vollstaendig flag. It is adequate to attempt a call but not complete enough to predict or interpret 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 units, ranges, and per-field meanings documented in the schema, so the baseline of 3 applies. The description mirrors those same concepts (Tankbestände, protokollierte Leerungen) without adding formula, ordering, or unit nuance beyond the schema.

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 action (rekonstruieren/recover) and a specific object (Kondensat over an observation period from start/end stock plus documented emptyings), which is far more precise than a tautology. It does not, however, distinguish itself from several close siblings (e.g. entfeuchter_tankleerung_zwei_zeitpunkte, entfeuchter_tank_zwischenablage_abgleichen, entfeuchter_energie_je_liter), so an agent cannot route between them on this text alone.

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 rather than stated: the reconstruction scenario (a bounded observation period with known start/end levels and logged emptyings) is clear from the wording, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer that other tank-related siblings serve different purposes.

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