Skip to main content
Glama

getecoback-raumklima

spuelmaschine_label_wasser_bezug

Read-only

Wassermessung je Spülgang mit dem vergleichbaren Eco-Labelwert abgleichen — Compare actual dishwasher litres per cycle with the applicable Eco label value.

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": {
      "gemessene_l": "<gemessene_l>",
      "gaenge": "<gaenge>",
      "label_l_pro_gang": "<label_l_pro_gang>",
      "eco_vergleichbar": "<eco_vergleichbar>"
    },
    "name": "spuelmaschine_label_wasser_bezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
gaengeYesZahl der vollständig gemessenen Maschinenzyklen.
gemessene_lYesGemessene Gesamtmenge in Litern für die erfassten Gänge.
eco_vergleichbarYesWurden ECO-Labelprogramm und vergleichbare Ladung gewählt und nur der Maschinenzulauf erfasst?
label_l_pro_gangYesLabelwert in Litern je Zyklus.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 safety is covered for free. Beyond that the description adds nothing: it doesn't say what happens when eco_vergleichbar is false, whether the result is an absolute delta or a ratio, or how the label value is applied. With no output schema, the description carries the entire burden here and does not take it on.

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?

The definition is short and front-loaded, but it is the same sentence rendered twice in German and English, which is pure duplication rather than added information. It's brief but not dense.

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?

There is no output schema, so the definition should disclose the shape of the result — a comparison delta, a pass/fail, or a per-cycle figure — and it does not. For a four-required-parameter calculation tool, an agent cannot tell what it will receive back or what happens with incomparable inputs.

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 all four parameters are already documented with types, ranges and text. The description only reinforces the per-cycle framing and the label comparison; it adds no new meaning about units or edge cases. 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 states a specific verb (abgleichen/compare) and a specific resource: actual litres per dishwasher cycle against the applicable Eco label value. An agent can distinguish this from load-comparison siblings such as spuelmaschine_beladung_vergleichen without opening the schema. It stops short of explicitly naming and excluding any alternative.

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 when-to-use statement, no prerequisite, and no named alternative. The only implicit condition lives in the parameter itself (eco_vergleichbar), not in the description, so the agent must infer that the tool is only meaningful when a comparable Eco program was run.

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