Skip to main content
Glama

getecoback-raumklima

luftkuehler_nachfuellfolge_wassertemperatur_rueckbezug

Read-only

Prüft ob die Wassertemperatur nach einer bereits erfolgten Nachfüllung wieder ins Vergleichsband zurückkehrte — Check when a recorded refill no longer differs from the prior tank-temperature band.

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": {
      "vorher_c": "<vorher_c>",
      "direkt_c": "<direkt_c>",
      "spaeter_c": "<spaeter_c>",
      "band": "<band>"
    },
    "name": "luftkuehler_nachfuellfolge_wassertemperatur_rueckbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandYesSelbst gewählte Temperaturbreite in °C.
direkt_cYesErste geeignete Ablesung nach der Nachfüllung in °C.
vorher_cYesWasserwert vor der dokumentierten Nachfüllung in °C.
spaeter_cYesSpätere Ablesung vor der Vergleichsprobe in °C.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 agent knows nothing is mutated. The description adds that this is a retrospective comparison against a previously recorded refill, which is useful context beyond the annotations. It does not disclose the actual comparison logic or what the result looks like (band membership, delta, boolean), and there is no output schema to fall back on.

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 operative clause is front-loaded and short, but the description is a bilingual duplicate: the English half is a loose translation that adds no new information and is actually less precise than the German. The second half therefore does not fully earn its place.

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 evaluation tool with no output schema, the description establishes the scenario but not the decision rule: it is unclear whether the comparison is direkt_c vs vorher_c against band, or spaeter_c vs band, or all three. The annotations cover the read-only nature, so the main remaining gap is the return semantics, which the agent must guess.

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 every parameter (vorher_c, direkt_c, spaeter_c, band) already carries units, ranges and German labels. The description only loosely reinforces the intended ordering of readings around the refill; it adds no syntax, defaults, or edge-case meaning (e.g. what happens when direkt_c falls outside band). Baseline 3 is appropriate.

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 verb ('Prüft') and a precise subject: whether water temperature returned to the comparison band after a completed refill. The English gloss is vaguer ('no longer differs from the prior tank-temperature band'), but together they let an agent identify the operation as a post-refill temperature-band check rather than a measurement or a general tank query. No sibling is named, so differentiation rests on the compound tool name.

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?

The phrase 'nach einer bereits erfolgten Nachfüllung' implies the only precondition: a refill must already be recorded. There is no statement of when to prefer this tool over the many sibling tank/temperature probes, no exclusion of cases (e.g. no refill recorded, missing later reading), and no guidance on interpreting an inconclusive result.

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