Skip to main content
Glama

getecoback-raumklima

luftkuehler_wasser_kalt_luftsignal_unter_messspiel

Read-only

Erkennt einen beobachteten kälteren Tank ohne entsprechend belegtes kühleres Auslasssignal — Distinguish a measured cooler tank from outlet cooling beyond measurement noise.

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": {
      "wasserabfall_c": "<wasserabfall_c>",
      "luftabfall_c": "<luftabfall_c>",
      "wasser_messspiel": "<wasser_messspiel>",
      "luft_messspiel": "<luft_messspiel>",
      "paare_passend": "<paare_passend>"
    },
    "name": "luftkuehler_wasser_kalt_luftsignal_unter_messspiel"
  }
}

Input Schema

NameRequiredDescriptionDefault
luftabfall_cYesGemessener korrigierter Auslassabfall relativ zur Einlasstemperatur in °C.
paare_passendYesBeide Änderungen aus vergleichbaren eigenen Zuständen und Zeitfenstern?
luft_messspielYesUnterscheidungsgrenze für die Luftmessung in °C.
wasserabfall_cYesGemessener Temperaturabfall im Wasser in °C.
wasser_messspielYesEigene Unterscheidungsgrenze für die Wassermessung in °C.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add real behavioral context — that the check is tolerance-aware and distinguishes genuine cooling from measurement noise — but it never says what the tool produces (a flag? a verdict? a numeric margin?), which matters because there is 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.

Conciseness3/5

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

The definition is short and front-loaded, but roughly half of it is a German/English duplication that restates the same idea rather than adding information. The English half earns little on its own; trimming or using the second clause to carry genuinely new detail would be better.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-required-parameter diagnostic comparison with no output schema, so the description must carry the burden of explaining the result. It explains the concept but not the outcome, and gives no indication of what constitutes a positive detection relative to the supplied Messspiel tolerances.

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 all five parameters (wasserabfall_c, luftabfall_c, wasser_messspiel, luft_messspiel, paare_passend) are already documented in the schema, including units and bounds. The description adds no further meaning about units, expected ranges, or how the two Abfall/Messspiel pairs interact, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does name a specific detection concept — a cooler tank whose outlet air signal does not corroborate the cooling — which is more than a restatement of the name. However, it is phrased abstractly ('beobachteten kälteren Tank ohne entsprechend belegtes kühleres Auslasssignal') and offers no differentiation from the many other luftkuehler_* diagnostic checks in the sibling set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when an agent should call this versus alternatives, no prerequisites, and no named sibling to route against. The closest thing to guidance is the implicit notion of comparing tank vs. outlet readings, which the caller must infer from the phrasing.

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