Skip to main content
Glama

getecoback-raumklima

luftkuehler_tank_marken_messwerte_abgrenzen

Read-only

Findet ein Volumenintervall aus zwei eigenen Füllmessungen um einen neuen Sichtstand — Bound volume from two measured fill observations surrounding a new level.

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": {
      "hierzu_unten_mm": "<hierzu_unten_mm>",
      "hierzu_oben_mm": "<hierzu_oben_mm>",
      "unten_ml": "<unten_ml>",
      "oben_ml": "<oben_ml>",
      "stand_mm": "<stand_mm>",
      "gleicher_tank": "<gleicher_tank>"
    },
    "name": "luftkuehler_tank_marken_messwerte_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
oben_mlYesBeim höheren Stand tatsächlich gemessenes Volumen in ml.
stand_mmYesNeuer Sichtstand in mm.
unten_mlYesBeim niedrigeren Stand tatsächlich gemessenes Volumen in ml.
gleicher_tankYesGleicher ruhender Tank und gleiche Bezugslinie in allen Ablesungen?
hierzu_oben_mmYesHöherer gemessener Stand in mm.
hierzu_unten_mmYesNiedrigerer gemessener Stand in mm.

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 agent knows this is a safe, closed computation. The description adds the useful fact that the result is a bounded interval rather than a single value, but it does not disclose the underlying assumption (e.g. interpolation between the two marks) or how the same-tank precondition is enforced.

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?

A single, front-loaded sentence with the verb first and zero padding. The bilingual duplication is mildly redundant but likely intentional for a German-language tool family, and nothing else is wasted.

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?

With six required numeric parameters and no output schema, the description should clarify the return shape and edge cases. It conveys the result type (volume interval) but not the units of the result, the behavior if the new level lies outside the measured bracket, or why the same-tank flag matters, leaving real gaps for a purely computational tool.

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% and every parameter carries a German description with units and ranges, so the schema does the heavy lifting. The tool description adds no parameter-level meaning, such as the relationship between hierzu_unten_mm/hierzu_oben_mm and stand_mm or the role of gleicher_tank, so the baseline of 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?

The description states a specific verb and resource: it finds ("Findet") a volume interval ("Volumenintervall") from two measured fill observations around a new sight level. That is concrete enough to distinguish it from measurement-collection siblings, although no sibling is named and the bracketing/computation nature is only implicit in "um einen neuen Sichtstand".

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 explicit when-to-use or when-not-to-use guidance and no alternative tool is referenced. The only usage signal is implicit: it requires two of your own fill measurements that surround the new level, but that precondition and any behavior when the level falls outside the bracket are never stated.

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