Skip to main content
Glama

getecoback-raumklima

entfeuchter_service_mengenablesung_spannweite

Read-only

Unsicherheit eines vorhandenen Messgefäß-Werts in die gemeldete Entnahme aufnehmen — Report a bounded collected-water rate from the readable graduation range.

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": {
      "unten_ml": "<unten_ml>",
      "oben_ml": "<oben_ml>",
      "gemessen_min": "<gemessen_min>",
      "gesamtes_wasser_erfasst": "<gesamtes_wasser_erfasst>"
    },
    "name": "entfeuchter_service_mengenablesung_spannweite"
  }
}

Input Schema

NameRequiredDescriptionDefault
oben_mlYesGrößter plausibler abgelesener Volumenwert in ml.
unten_mlYesKleinster plausibler abgelesener Volumenwert in ml.
gemessen_minYesGemessene Zeit des dokumentierten Intervalls in Minuten.
gesamtes_wasser_erfasstYesIn diesem Intervall nur aus dem Gerät stammendes und vollständig aufgefangenes Wasser?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 useful framing — that the tool handles the uncertainty of an already-measured vessel value rather than taking a fresh reading — but it does not state what the returned rate represents, over what timeframe it is expressed, or how it treats the bounds. The German 'in die gemeldete Entnahme aufnehmen' also slightly suggests mutating a reported figure, which sits uneasily beside readOnlyHint=true, though the English rendering reads as a computed report, so this is ambiguity rather than contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the same idea is stated twice with slightly different emphases (German uncertainty-folding vs. English bounded-rate reporting), which costs tokens without resolving the ambiguity. The core action is front-loaded, which helps.

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?

All four required parameters are covered by the schema and there is no output schema, so full return-value documentation is not mandatory. Still, for a derived-quantity tool the description should at least indicate what the resulting rate is (per hour? per day? per interval?) and how the boolean capture flag affects the result; that is missing.

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%, so each of the four parameters (unten_ml, oben_ml, gemessen_min, gesamtes_wasser_erfasst) is already documented in the schema. The description adds only the relational idea that the two ml bounds form the graduation span feeding the rate; it offers no units, defaults, or interaction notes beyond that.

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: report a bounded collected-water rate derived from a readable graduation range, with an explicit hint that it folds measurement uncertainty into the reported extraction. It is distinguishable in substance from dehumidifier siblings, but it never names or contrasts any of them, so the agent must infer the boundary itself.

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: use it when you have an uncertain vessel reading bounded by a min/max graduation range and want a defensible extraction figure. There is no explicit when-to-use, no when-not-to-use, and no pointer to an alternative sibling such as entfeuchter_energie_je_liter or entfeuchter_nennwert_und_messvolumen_scope.

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