Skip to main content
Glama

getecoback-climate-weather

luftkuehler_fuellsicht_minimum_ohne_interpolation

Read-only

Ordnet einen vorhandenen Sichtstand den dokumentierten Mindest- und Höchstzeichen zu — Place a measured tank level against documented fill marks without inferring volume.

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": {
      "untere_marke_mm": "<untere_marke_mm>",
      "obere_marke_mm": "<obere_marke_mm>",
      "iststand_mm": "<iststand_mm>",
      "bezug_abgeglichen": "<bezug_abgeglichen>"
    },
    "name": "luftkuehler_fuellsicht_minimum_ohne_interpolation"
  }
}

Input Schema

NameRequiredDescriptionDefault
iststand_mmYesBeobachteter ruhender Füllstand in mm.
obere_marke_mmYesHöhe der dokumentierten Höchstmarke ab demselben Nullpunkt in mm.
untere_marke_mmYesHöhe der dokumentierten Mindestmarke ab demselben Nullpunkt in mm.
bezug_abgeglichenYesMontagelage und beide Markierungen gelten nachweislich für diesen Tank und Betriebszustand?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds a genuine behavioral constraint beyond that — no interpolation, no volume inference — but says nothing about outcome when iststand_mm falls outside the documented marks, or what the result contains.

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 short sentences, front-loaded with the action and followed by the scope limit; nothing is buried. The German and English halves are semantically identical, which is mild redundancy rather than waste.

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?

It is adequate for a simple, fully required, fully documented four-parameter read-only comparison. However, the required boolean gate bezug_abgeglichen (mounting position and marks verified for this tank) is never explained behaviorally — an agent cannot tell whether false blocks the call — and out-of-range mark handling is unaddressed.

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% with per-parameter descriptions in German, so the schema already carries the parameter meaning. The description only restates the measured-level and mark concepts at a high level and adds no units, tolerance, or handling detail beyond the schema.

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 concrete verb and resource: it assigns an existing sight level (Sichtstand/measured tank level) to the documented minimum and maximum marks. The trailing scope clause 'without inferring volume' rules out the interpolation variant, so an agent can tell this apart from level-to-volume calculations, though it doesn't name which sibling to use instead.

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

Usage Guidelines4/5

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

It gives clear usage context — you need an already measured standing level plus documented min/max marks — and states an explicit exclusion: do not interpolate or derive volume. No named alternative tool is offered, so the routing guidance stops short of a full when/when-not/alternative statement.

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