Skip to main content
Glama

getecoback-raumklima

waschmittel_packung_alter_dosierplan_abgleich

Read-only

Gleiche Härte, Wäschemenge und Verschmutzung an aktueller Packung und altem Dosierplan vergleichen — Reconcile a saved detergent dose with the package currently in use.

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": {
      "aktuelle_packung": "<aktuelle_packung>",
      "gleicher_tabellenbezug": "<gleicher_tabellenbezug>",
      "packung_ml": "<packung_ml>",
      "alter_plan_ml": "<alter_plan_ml>"
    },
    "name": "waschmittel_packung_alter_dosierplan_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
packung_mlYesDafür auf der aktuellen Packung abgelesene ml. Bei fehlendem Beleg 0.
alter_plan_mlYesDafür gespeicherte ml im alten Dosierplan. Bei fehlendem Beleg 0.
aktuelle_packungYesIst die Dosierangabe genau der jetzt verwendeten Packung lesbar?
gleicher_tabellenbezugYesBeziehen sich beide Werte auf dieselbe Wasserhärte, denselben Verschmutzungsgrad und dieselbe Wäschemenge?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a pure read/compare operation. It adds useful context about which three dimensions must match (hardness, laundry amount, soiling), but it says nothing about what the comparison yields, how mismatches or missing values are treated, or that the call has no side effects on the stored plan.

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?

The comparison basis and purpose are front-loaded in a single compact German sentence, with an English gloss appended. The bilingual duplication is mild redundancy but serves the stated purpose; there is no filler or backtracking.

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?

With no output schema, the description is the only place to learn what a reconciliation returns (a verdict, a delta, a list of discrepancies), and it is silent on this. Inputs are fully covered by the schema and the safety profile by annotations, so the gap is narrow but material for a comparison tool whose entire value is its result.

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 each parameter is documented in-schema, including the enum for aktuelle_packung and the 0-for-missing convention, so the description need not compensate. The description adds only a restatement of the comparison basis, which maps to gleicher_tabellenbezug but gives no extra semantics for packung_ml vs. alter_plan_ml beyond their names.

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 ("Gleiche ... vergleichen" / "Reconcile a saved detergent dose with the package currently in use") and the resource (current package vs. old dosing plan). It is clearly a comparison/reconciliation tool rather than a lookup, but it never names or contrasts a sibling such as waschmittel_dosiertabelle_wasserhaerte_intervall, so an agent must infer the boundary.

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: the tool is for the situation where a package changed and an old dosing plan must be checked against it. There is no explicit when-to-use, when-not-to-use, or named alternative, and no statement about what to do when the reference basis does not match (gleicher_tabellenbezug=false).

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