Skip to main content
Glama

getecoback-climate-weather

luftkuehler_kuehlakku_pegelversatz_tank

Read-only

Prüft ob sich die Sichtmarke bei gleicher abgemessener Wassermenge mit dem dokumentierten Kühlakku verschiebt — Compare measured tank levels at a fixed water volume with and without a documented cooling pack.

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": {
      "ohne_mm": "<ohne_mm>",
      "mit_mm": "<mit_mm>",
      "gleicher_inhalt": "<gleicher_inhalt>",
      "akku_belegt": "<akku_belegt>"
    },
    "name": "luftkuehler_kuehlakku_pegelversatz_tank"
  }
}

Input Schema

NameRequiredDescriptionDefault
mit_mmYesBereits gemessener Stand mit Kühlakku ab derselben Linie in mm.
ohne_mmYesBereits gemessener Stand ohne Kühlakku in mm.
akku_belegtYesAkku und beobachtete Einlage sind in der Anleitung für diesen Tank beschrieben.
gleicher_inhaltYesGleiche abgemessene Wassermenge und gleiche ruhende Tanklage?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 useful framing — the comparison requires equal measured volume and a documented cooling pack — but says nothing about what the result looks like (a shift verdict, a delta in mm) or how it is reported, which matters because no output schema exists.

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?

One front-loaded sentence with the comparison condition stated before the colon-style clarification, and no filler. The full bilingual duplication adds length without new information, which keeps it from a 5.

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?

A read-only check with four required, fully described parameters is adequately framed, but with no output schema the description should say what a passing or shifting result means and whether a magnitude is returned. That omission is the main remaining gap for a tool whose entire value is the verdict.

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 coverage is 100%, so all four parameters are already documented with bounds and meaning. The description only reinforces the shared frame of the two boolean flags (same water volume, documented pack) without adding format or edge-case guidance beyond the schema, so the 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?

States a specific verb and resource: it checks whether the visible tank mark shifts at an identical measured water volume when the documented cooling pack is used versus not. The bilingual restatement reinforces the comparison nature of the check rather than adding sibling differentiation, and no alternative tool is named, so it stops short of a 5.

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 description embeds a precondition (a documented cooling pack exists for this tank, mirrored by the akku_belegt flag) but gives no explicit when-to-use, when-not-to-use, or alternative. With many near-neighbour tools in the family, an agent is left to infer the selection criteria from the name and parameters alone.

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