Skip to main content
Glama

getecoback-climate-weather

waschmittel_dosiertabelle_wasserhaerte_intervall

Read-only

Waschmittel-Dosierspalten bei schwankender Wasserhärte am Anschluss bestimmen — Identify every hardness column supported by a recorded local interval.

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": {
      "anschlussbezug": "<anschlussbezug>",
      "einheit": "<einheit>",
      "minimum": "<minimum>",
      "maximum": "<maximum>",
      "packung": "<packung>"
    },
    "name": "waschmittel_dosiertabelle_wasserhaerte_intervall"
  }
}

Input Schema

NameRequiredDescriptionDefault
einheitYesEinheit und Grundlage der Gesamthärte. Keine Zahl aus ppm oder Carbonathärte übernehmen.
maximumYesObere belegte Gesamthärte in derselben Einheit und am selben Anschluss.
minimumYesUntere belegte Gesamthärte in mmol CaCO₃/L. Bei unbekannter Einheit Wert nicht auswertbar.
packungYesLesbarkeit der Härtespalten am aktuellen Mittel.
anschlussbezugYesSind Quelle, Zeitpunkt und der Waschmaschinenanschluss eindeutig zugeordnet?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered; the description reinforces that the input is a 'recorded local' interval rather than an open-world lookup. Beyond that it adds little: it does not say what the tool returns when the interval is only partially covered, nor how gaps in the interval are reported back. With annotations carrying the safety profile, this is an adequate but thin contribution.

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?

One front-loaded sentence with the resource first and the qualifying condition after the dash — efficient and scannable. The German and English halves are largely duplicative, which costs a little, but no sentence is wasted overall.

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?

All five inputs are required and well documented in the schema, and the description states the goal of identifying supported hardness columns. With no output schema, however, the description should say what the result looks like (column list, boundary handling for '-' intervals, behavior when packung is 'teilweise_oder_offen'), which it omits.

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 three of five parameters are enums with their own documented semantics (e.g. the warning not to use ppm or carbonate hardness, and that an unknown unit makes the value unusable). The description adds no parameter-level meaning beyond the schema, 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 names a specific verb and object ('Waschmittel-Dosierspalten ... bestimmen' / 'Identify every hardness column') plus the qualifying condition of a fluctuating, locally recorded hardness interval, so the operation is understandable. It does not, however, distinguish itself from near-identical siblings such as miele_g7673_schwankende_wasserhaerte_oberwert or waschmittel_packung_alter_dosierplan_abgleich, leaving the agent to guess which one applies.

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 named. The phrase 'bei schwankender Wasserhärte' implies a context but does not tell the agent what to do when hardness is stable, when the interval is unknown, or how this differs from the sibling derivations.

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