Skip to main content
Glama

getecoback-raumklima

fenstersauger_unterkante_auffangprobe_verlagerung

Read-only

Bei zwei vergleichbaren Fensterläufen Wasser im Gerät und Tropfen unter dem Rahmen getrennt beurteilen — Check whether a change merely moves captured water out of the tank.

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": {
      "tank_a_ml": "<tank_a_ml>",
      "tank_b_ml": "<tank_b_ml>",
      "unten_a_ml": "<unten_a_ml>",
      "unten_b_ml": "<unten_b_ml>",
      "gleiche_flaeche_und_naesse": "<gleiche_flaeche_und_naesse>"
    },
    "name": "fenstersauger_unterkante_auffangprobe_verlagerung"
  }
}

Input Schema

NameRequiredDescriptionDefault
tank_a_mlYesGemessene Wassermenge im Tank nach A in Millilitern.
tank_b_mlYesTankmenge nach B.
unten_a_mlYesSeparat gemessene Auffangmenge unter der Kante in A.
unten_b_mlYesSeparat gemessene Auffangmenge unter der Kante in B.
gleiche_flaeche_und_naesseYesWaren Fläche, Ausgangsnässe und Sammelgrenze gleich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety is covered. The description adds real interpretive content — that tank and under-frame water must be judged separately to detect pure displacement rather than genuine pickup — but says nothing about what the tool returns (a verdict, a delta, a ratio) and there is no output schema to fill that gap.

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 sets the precondition, then the evaluation question, with no filler. The mixed German/English wording is slightly awkward but does not cost clarity.

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 five required numeric/boolean parameters fully documented and a read-only profile supplied by annotations, the essential calling information is present. What is missing is any indication of the result — threshold, tolerance, or expected conclusion — which for an analysis tool with no output schema leaves a meaningful gap.

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%, including units, bounds and the equal-surface/equal-wetness gate, so the baseline is 3. The description's framing of 'Wasser im Gerät' versus 'Tropfen unter dem Rahmen' gives conceptual meaning to the tank_* and unten_* parameter pairs beyond raw naming, but adds no measurement or comparison rules.

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 comparison task: separately judging tank water versus droplets under the frame across two comparable window-cleaning runs, and states the analytic question (does a change merely displace captured water?). The verb 'beurteilen/Check' plus the resource (tank vs. under-frame catch sample) is specific enough that an agent can distinguish it from a plain measurement tool, though it never names or contrasts any sibling.

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

Usage Guidelines3/5

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

It gives a clear precondition — 'bei zwei vergleichbaren Fensterläufen' — reinforced by the required same-surface/same-wetness guard parameter, so the agent knows the scenario. It offers no when-not guidance, no prerequisites about measurement procedure, and no alternatives, so usage is implied rather than prescribed.

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