Skip to main content
Glama

getecoback-climate-weather

spueler_reinigerdosis_fachmarke_fuellmaximum

Read-only

Reiniger-Dosierung auf dem Etikett von der Füllgrenze des Reinigerfachs trennen — Distinguish package dose, chamber capacity and the fallback exact-model guidance.

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>",
      "reiniger": "<reiniger>",
      "packungsbezug": "<packungsbezug>",
      "packungsmenge_ml": "<packungsmenge_ml>",
      "manuell_und_normale_beladung": "<manuell_und_normale_beladung>"
    },
    "name": "spueler_reinigerdosis_fachmarke_fuellmaximum"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesGenaue Gerätevariante.
reinigerYesDokumentierte Form des manuell dosierten Geschirrspülreinigers.
packungsbezugYesPassende Dosisangabe für den Fall.
packungsmenge_mlYesBelegter Packungswert in ml, sonst 0.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?
manuell_und_normale_beladungYesManuelles Fach und gewöhnliche Beladung für den gewählten Beleg bestätigt?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-domain advisory operation. The description adds that the result is a separation of two dose concepts rather than a single number, which is useful framing. It does not say what the response looks like, how missing or unconfirmed confirmations (anleitung_bestaetigt, manuell_und_normale_beladung) alter the answer, or whether the tool can refuse to give a dose.

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 front-loaded sentence with the key distinction stated first, followed by the fallback clause. The German/English double phrasing is slightly redundant but short enough not to be wasteful, and there is no filler.

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?

The schema is fully documented and annotations cover the safety profile, so the agent can construct a call. What is missing is the output side: with no output schema and six required parameters, the description never says whether the tool returns a dose recommendation, a confirmation, or a warning, which is exactly the gap the description should close here.

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 parameters carry enums with per-value descriptions, so the schema carries essentially all parameter meaning. The description mentions package dose, chamber capacity and fallback model guidance, which loosely maps onto packungsbezug and modell but adds no format, unit, or edge-case detail beyond the schema. Baseline 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 distinction the tool performs: separating the detergent dose printed on the package label from the fill limit of the rinse-aid/cleaner compartment, plus a fallback path to exact-model guidance. That is a concrete operation on a concrete subject, not a restatement of the name. It does not, however, contrast itself with near neighbours such as spueler_salz_klarspueler_reiniger_fachbeleg or spueler_multitab_salzgrenze_packung_geraet.

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 statement, no prerequisites, and no naming of alternatives. The phrase 'fallback exact-model guidance' faintly implies that a model-unknown branch exists, but the agent is left to infer that from the model enum rather than from guidance in the description.

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