Skip to main content
Glama

getecoback-raumklima

entfeuchtung_sammelsystem_beide_wege_abgleich

Read-only

Gemeinsame Kondensatmessung mit getrennt beobachtetem Tank- und Schlauchanteil abgleichen — Reconcile asynchronous collection paths without silently ignoring a differing observation window.

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": {
      "sammlung_gesamt_l": "<sammlung_gesamt_l>",
      "tank_l": "<tank_l>",
      "schlauch_l": "<schlauch_l>",
      "transfer_l": "<transfer_l>",
      "gleicher_stichtag": "<gleicher_stichtag>"
    },
    "name": "entfeuchtung_sammelsystem_beide_wege_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
tank_lYesSeparat erfasster Tankanteil im Messfenster.
schlauch_lYesSeparat erfasste Kondensatmenge im Schlauchweg im Messfenster.
transfer_lYesDavon nachweislich bereits im Tank gezählte und anschließend nochmals im Schlauchweg erfasste Menge.
gleicher_stichtagYesGleiche Zeitgrenzen und vollständige Berücksichtigung etwaiger Restmengen an beiden Wegen?
sammlung_gesamt_lYesUnabhängig belegte Gesamtmenge aus beiden Geräten oder Erfassungswegen im Messfenster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 is covered. The description adds the behavioral intent of not silently swallowing a mismatched observation window, but does not say what the reconciliation actually returns or how a mismatch is surfaced (error, flag, adjusted value), which matters with no output schema.

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 compact clauses, German then English, with the action front-loaded. The bilingual restatement is somewhat redundant but short enough that no sentence feels 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 five-required-parameter, no-output-schema reconciliation tool, the description covers the input framing but says nothing about the return value or result semantics. An agent can call it, but cannot predict whether a mismatch yields an error, a warning, or a reconciled figure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3; the description earns a small bump by framing the parameters conceptually — separate tank/hose portions versus a combined measurement, and the 'differing observation window' caveat that maps directly to gleicher_stichtag and the transfer_l double-counting concern.

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 German clause names a specific action (abgleichen/reconcile) on a specific resource (gemeinsame Kondensatmessung with separately observed Tank- and Schlauchanteil). It is distinguishable from the many other *_abgleich siblings by the condensate tank/hose framing, though distinctions rely on the domain wording rather than an explicit contrast with a named sibling.

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 'Reconcile asynchronous collection paths without silently ignoring a differing observation window' implies the use case: when the two collection paths were observed over non-identical windows. However, it never states when not to use it, nor names any alternative tool for the single-path or same-window case.

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