Skip to main content
Glama

getecoback-raumklima

spuelroutine_vorspuelwasser_belegte_ladungen

Read-only

Gemessenes zusätzliches Vorspülwasser auf die tatsächlich bearbeiteten Ladungen beziehen — Isolate pre-rinse water from the machine’s measured cycle 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": {
      "mit_vorspuelen": "<mit_vorspuelen>",
      "ohne_vorspuelen": "<ohne_vorspuelen>",
      "vorspuel_l": "<vorspuel_l>",
      "maschinen_l": "<maschinen_l>",
      "bilanzbereiche_getrennt": "<bilanzbereiche_getrennt>"
    },
    "name": "spuelroutine_vorspuelwasser_belegte_ladungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorspuel_lYesFür die erste Gruppe separat gemessener Vorspülverbrauch.
maschinen_lYesGemessener Maschinenverbrauch zusammen über beide Gruppen.
mit_vorspuelenYesVollständig beobachtete Ladungen mit einer zusätzlichen Vorspülhandlung.
ohne_vorspuelenYesVollständig beobachtete Ladungen ohne zusätzliche Vorspülhandlung.
bilanzbereiche_getrenntYesWurde das Vorspülen außerhalb der Maschinenmessung erfasst?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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 little beyond that: it does not say how the split is computed, whether the result is per-load or aggregate, how the two load counts act as denominators, or what happens if vorspuel_l exceeds maschinen_l or if both load counts are zero. For a pure arithmetic tool with edge cases, this is a meaningful gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but it spends a whole clause on an English restatement that largely duplicates the German sentence rather than extending it. The duplicated framing is waste in a definition that could have used those words to state the returned quantity.

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

Completeness2/5

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

With five required parameters and no output schema, the description carries the burden of explaining what comes back, yet it never says whether the result is liters per load, a corrected cycle volume, or a ratio. Given that the tool exists solely to produce a computed figure, this omission leaves the definition incomplete for correct invocation.

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%, so the schema already explains each of the five parameters, and the baseline of 3 applies. The description adds no parameter-level meaning beyond the schema — in particular it never explains how bilanzbereiche_getrennt alters the computation or that mit_vorspuelen and ohne_vorspuelen are the normalizing denominators.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The two clauses together convey a calculation: relate measured extra pre-rinse water to the loads actually processed, isolating pre-rinse volume from the machine's measured cycle volume. That is more specific than a tautology, but the description never states plainly that this is a read-only computation tool nor what quantity it produces, and the German and English halves only partially align ('auf die Ladungen beziehen' vs. 'isolate ... from the machine's measured cycle volume'). No sibling differentiation is offered, though the sibling names are in unrelated domains so there is no obvious alternative to name.

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 guidance on when this tool should be used, no preconditions (e.g. that it applies only when pre-rinsing was measured outside the machine reading), and no reference to any alternative tool. The agent must infer the use case entirely from the name and description.

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