Skip to main content
Glama

getecoback-raumklima

spueler_weichwasser_ohne_salz_geraetemodell

Read-only

Bei belegtem Weichwasser den getrennten Salzfall des exakten Modells prüfen — Use the model-specific soft-water boundary without relying on a multi-function tablet.

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>",
      "zulauf": "<zulauf>",
      "maximal_dh": "<maximal_dh>"
    },
    "name": "spueler_weichwasser_ohne_salz_geraetemodell"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesGenaues Modell aus den deutschen Unterlagen.
zulaufYesBezug des Härtebereichs.
maximal_dhYesBelegter Zahlenwert der Wasserhärte am Zulauf in °dH.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?

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 only declare readOnlyHint=true and openWorldHint=false, so the description must still explain what the check yields and how the "anderes_oder_offen" branch behaves. It adds only the vague notion of a model-specific soft-water boundary and says nothing about results, limits, or edge cases. No contradiction with the annotations, but little value added.

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?

A single compact statement with the condition front-loaded and no filler. The bilingual construction is slightly awkward but does not waste space. Nothing is buried.

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?

Four required parameters, two enums, and no output schema mean the description should clarify the return value and how uncertain model or intake values are handled. It does neither, leaving the agent unable to predict the outcome of the call. For a lookup-style tool with no output schema, this is a meaningful omission.

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% with two enums, so the schema already defines every parameter including the model list and the °dH range. The description's "exakten Modells" merely echoes the modell parameter. Baseline 3 is appropriate since the schema carries the semantic load.

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 description names a verb and object ("getrennten Salzfall des exakten Modells prüfen") under a stated condition ("bei belegtem Weichwasser"), so the general intent is graspable. However, it never says what the check actually produces or decides, and it does not distinguish this from nearby salt/rinse-aid or hardness-table tools. An agent knows roughly what domain it is in but not precisely what the tool does.

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?

"Bei belegtem Weichwasser" provides a genuine triggering condition, and "without relying on a multi-function tablet" signals an exclusion of a non-tool alternative. Neither a sibling tool nor a when-not-to-use case is named, so the routing guidance stays implicit. Adequate but with clear gaps.

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