Skip to main content
Glama

getecoback-raumklima

luftkuehler_wasserverlust_stillstand_kontrolllauf

Read-only

Vergleicht Tankabnahmen bei regulärem Betrieb und beobachtetem Stillstand in demselben Zustand — Compare active-mode and stopped reservoir changes under matched conditions.

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": {
      "abnahme_aktiv_ml": "<abnahme_aktiv_ml>",
      "abnahme_ruhe_ml": "<abnahme_ruhe_ml>",
      "gleiche_dauer": "<gleiche_dauer>"
    },
    "name": "luftkuehler_wasserverlust_stillstand_kontrolllauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
gleiche_dauerYesDauern, Standort, Startmenge und Mattenzustand wurden für beide Blöcke abgeglichen?
abnahme_ruhe_mlYesTankabnahme im separaten Ruheblock in ml.
abnahme_aktiv_mlYesTankabnahme während des aktiven Blocks 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 safety profile is covered. The description adds the behavioral framing that the comparison is only meaningful under matched conditions, which is genuinely useful. It does not, however, state what the comparison yields (delta, ratio, verdict) or how unequal durations are handled.

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 bilingual sentence with the comparison target front-loaded and the conditioning clause second; no filler. The German/English duplication is redundant for an agent but does not obscure meaning.

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 simple read-only, three-parameter comparison tool with full schema coverage, the description covers the inputs adequately. With no output schema, however, the description should indicate what the comparison produces and how the gleiche_dauer gate affects the result; that is left unstated.

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 of the three parameters (active withdrawal, rest withdrawal, matched-conditions flag) is fully documented in the schema itself. The description's 'matched conditions' wording loosely reinforces gleiche_dauer but adds no units, bounds, or interpretation beyond what the schema already provides. 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 verb and resource: comparing reservoir withdrawal (Tankabnahme) between an active block and an observed standstill block under matched conditions. An agent can tell it is a two-block comparison tool rather than a single measurement. However, it does not distinguish itself from close siblings such as luftkuehler_tankstand_ruecklauf_nach_stopp or luftkuehler_vergleich_ein_tankvolumen_getrennte_laufarten, which an agent would have to resolve on its own.

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?

The phrase 'in demselben Zustand' / 'under matched conditions' implies the tool is for controlled active-vs-stopped comparisons, which is useful context. But there is no explicit when-to-use statement, no exclusion of alternatives, and no guidance on what to do when conditions cannot be matched (other than the required boolean). Usage must be inferred.

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