Skip to main content
Glama

getecoback-raumklima

bosch_spueler_haertetabelle_eingabeeinheit_grenze

Read-only

Den Gerätewert für SBV4EBX00D oder SKS62E32EU aus der jeweiligen Wasserhärtetabelle lesen — Look up the exact Bosch hardness setting without interpolating across printed rows.

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>",
      "wert": "<wert>",
      "einheit": "<einheit>"
    },
    "name": "bosch_spueler_haertetabelle_eingabeeinheit_grenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
wertYesWert in der angegebenen Einheit, unverändert aus dem Beleg übernommen.
modellYesGenaues Bosch-Modell aus den deutschen Unterlagen.
einheitYesEinheit der bestätigten Wasserhärte: dh = °dH, mmol = mmol/l aus demselben Zulaufbeleg.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?
zulaufwert_bestaetigtYesDer Zahlenwert gehört zum Zulauf des konkreten Geschirrspülers?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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. The description adds one real behavioral fact: the result is the exact table entry, not an interpolated value. It stays silent on the edge cases the name implies ('grenze'), e.g. what is returned or whether the call fails when modell is 'anderes_oder_offen' or einheit is 'offen'.

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?

Two short sentences with the operation and the key constraint front-loaded; nothing is padded or tangential. The German and English sentences largely restate each other, which is a minor redundancy even allowing for bilingual phrasing.

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

Completeness5/5

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

For a read-only, five-required-parameter lookup with no output schema, the description supplies what an agent needs: the source table, the supported models, and the exactness guarantee. The remaining details (unit handling, fallback path) are carried by the fully-described schema fields with enum values.

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 all five parameters documented including enum values and the confirmation booleans, so the baseline is 3. The description reinforces that the two enumerated models come from German documentation, but adds no meaning about how 'einheit' ('dh' vs 'mmol') is handled or what the '{anderes_oder_offen}' fallback does.

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 concrete verb ('read from the table') and resource (the device hardness value), and pins it to two explicit model identifiers (SBV4EBX00D, SKS62E32EU). The clause 'without interpolating across printed rows' distinguishes it from a general hardness-range/step mapping sibling, though no sibling is named outright.

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 statement of when to call this versus the hardness-range or salt-limit siblings, and no when-not guidance. The only usable cue is the negative constraint about not interpolating, which shapes the answer but not the routing decision. An agent must infer the call condition from the required confirmation booleans in the schema.

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