Skip to main content
Glama

getecoback-raumklima

spueler_multitab_salzgrenze_packung_geraet

Read-only

Die Salzersatz-Angabe eines Multitabs an Geräteanleitung und tatsächlicher Wasserhärte prüfen — Intersect verified detergent and device limits before considering that use case.

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": {
      "modell": "<modell>",
      "anleitung_bestaetigt": "<anleitung_bestaetigt>",
      "zulaufwert_bestaetigt": "<zulaufwert_bestaetigt>",
      "wasserhaerte_dh": "<wasserhaerte_dh>",
      "packung": "<packung>",
      "packung_untergrenze_dh": "<packung_untergrenze_dh>",
      "packung_obergrenze_dh": "<packung_obergrenze_dh>"
    },
    "name": "spueler_multitab_salzgrenze_packung_geraet"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesGenaues Modell aus den deutschen Unterlagen.
packungYesWas belegt der Reiniger-Aufdruck?
wasserhaerte_dhYesBelegter Zahlenwert der Wasserhärte am Zulauf in °dH.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?
packung_obergrenze_dhYesBelegte obere Packungsgrenze in °dH.
zulaufwert_bestaetigtYesWert gilt tatsächlich am Zulauf dieses Geräts?
packung_untergrenze_dhYesBelegte untere Packungsgrenze in °dH. Bei einer reinen Bis-Angabe 0.

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 nothing beyond that: it does not say what happens when the tab's salt limit falls outside the water hardness range, whether a mismatch blocks the use case, or what the verification returns. With no output schema, this leaves the decision consequence undisclosed.

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 the em-dash second clause is redundant with the first and mixes English into a German definition, adding confusion rather than information. The German half earns its place; the English half does not.

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?

Seven required parameters with no output schema and no annotations describing return shape means the description must explain what a successful verification yields and what to do with a boundary violation. It does neither, leaving an agent unable to interpret the result of a fairly involved domain check.

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%: all seven parameters carry descriptions, and both enums (modell, packung) are enumerated with their values. The description adds no additional meaning about how, e.g., packung_untergrenze_dh interacts with wasserhaerte_dh, so the baseline 3 applies.

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 first clause names a concrete check (Salzersatz-Angabe eines Multitabs vs. Geräteanleitung und tatsächlicher Wasserhärte), which is more specific than a restated name. But the second clause ('Intersect verified detergent and device limits before considering that use case') is abstract and language-switched, and nothing distinguishes this from near-siblings like waschmittel_packung_alter_dosierplan_abgleich. An agent can guess the domain but not the precise operation.

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?

'Before considering that use case' gestures at a pre-check gate but never says which use case, what a passing vs. failing outcome means, or which sibling to use instead. No when-not guidance and no named alternative, leaving selection between the many spueler_* checks to the agent's guesswork.

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