Skip to main content
Glama

getecoback-raumklima

spueler_nach_salzbehaelter_oeffnen_spuelbezug

Read-only

Die modelleigene Vorgabe nach Salzkontakt vom regulären Spülgang unterscheiden — Identify the documented after-fill or opened-cap case for the exact dishwasher manual.

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>",
      "vorgang": "<vorgang>"
    },
    "name": "spueler_nach_salzbehaelter_oeffnen_spuelbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesGenaues Modell aus den deutschen Unterlagen.
vorgangYesBeobachteter Vorgang am eindeutig gekennzeichneten Salzbehälter.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and openWorldHint=false, so the agent already knows this is a safe, closed-world lookup, and nothing in the description contradicts that. What the description adds beyond the annotations is modest: it stresses model-specificity and reliance on the confirmed manual. It does not say what happens for the 'anderes_oder_offen' or 'offen' cases, which is the behavior an agent would most want clarified.

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, but it is a bilingual restatement of the same idea: the German clause and the English clause cover largely the same ground. That duplication consumes a large share of the text and leaves the most useful detail (what the tool returns) unaddressed. Structure is front-loaded but redundant.

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?

Three required parameters, two enumerations, and no output schema — so the description carries the burden of explaining the result, and it does not. It never states whether the output is the manual's prescribed rinse step, a differentiated procedure, or an uncertainty flag. For a classification tool with no return-value documentation, that is a meaningful gap.

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 enumerated parameters, so the schema already carries the semantics and the baseline is 3. The description reinforces two of them — 'exact dishwasher manual' for 'modell' and 'after-fill or opened-cap' for 'vorgang' — but adds no disambiguation between 'salz_eingefuellt' and 'nur_salzdeckel_geoeffnet', the distinction the tool's name hinges on.

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 operation — distinguishing the model's prescribed procedure after salt contact from the regular rinse cycle, and identifying the documented after-fill or opened-cap case for a given manual. The verb+resource combination ('unterscheiden' / 'Identify ... case') is concrete enough to separate it from siblings about salt refilling or salt product labelling. It stops short of a full 5 because the returned 'Vorgabe' is never characterized as an artifact an agent would recognize.

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?

Usage is only implied: an agent can infer it applies when salt was filled or the cap merely opened, matching the 'vorgang' enum. There is no explicit statement of when not to use it and no sibling is named as the alternative for the adjacent cases (e.g. first-fill/refill or salt-product identification). Routing therefore rests on inference from the enum values rather than on stated guidance.

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