Skip to main content
Glama

getecoback-raumklima

fenstersauger_wv8_herstellergrenzen_doppelengpass

Read-only

Prüfe Laufzeit und Tankvolumen des WV 8 Signature Line gegen einen vollständig gemessenen Durchgang — Check which documented WV 8 limit binds for a measured task

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": {
      "variante_16337850": "<variante_16337850>",
      "aktive_zeit_min": "<aktive_zeit_min>",
      "gesammeltes_wasser_ml": "<gesammeltes_wasser_ml>",
      "ohne_pause_geplant": "<ohne_pause_geplant>"
    },
    "name": "fenstersauger_wv8_herstellergrenzen_doppelengpass"
  }
}

Input Schema

NameRequiredDescriptionDefault
aktive_zeit_minYesAus einem vergleichbaren Versuch benötigte aktive Minuten
variante_16337850YesWV 8 Signature Line, Artikel 1.633-785.0 bestätigt
ohne_pause_geplantYesDie Aufgabe soll in einer einzigen Akku- und Tankphase abgeschlossen werden
gesammeltes_wasser_mlYesIm vergleichbaren Versuch aufgefangene Wassermenge

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 that this is a two-constraint comparison against documented manufacturer limits and reports the binding one, but says nothing about behavior at or beyond the limits, tolerance handling, or ordering of the two checks.

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?

It is short and front-loads the check, but the German sentence is immediately restated in English with essentially the same content, which is mild redundancy rather than added information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, fully documented, read-only comparison tool with no output schema, the description conveys input expectation (a complete measured run) and the nature of the result (which limit binds). Only the handling of inputs that exceed both limits is left unstated.

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 the schema already explains all four parameters. The description only loosely maps 'Laufzeit' and 'Tankvolumen' onto aktive_zeit_min and gesammeltes_wasser_ml without adding format or validity details, 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?

The description names a specific verb ('Prüfe'/'Check') and two concrete resources (Laufzeit and Tankvolumen of the WV 8 Signature Line), plus the outcome ('which documented WV 8 limit binds'). That is enough to distinguish it from generic measurement siblings, though it never names an adjacent tool it could be confused with.

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?

Usage is only implied: 'gegen einen vollständig gemessenen Durchgang' suggests it needs a completed comparable measurement, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for incomplete or unmeasured cases.

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