Skip to main content
Glama

getecoback-climate-weather

spuelprogramm_anzeige_istvergleich_extras_und_beladung

Read-only

Zwei belegte Ist-Anzeigewerte nur mit vergleichbarer Programmauswahl und Beladung einordnen — Keep same-program displayed actuals comparable.

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": {
      "a_liter": "<a_liter>",
      "b_liter": "<b_liter>",
      "gleiches_programm": "<gleiches_programm>",
      "gleiche_extras": "<gleiche_extras>",
      "beladung_und_umgebung_vergleichbar": "<beladung_und_umgebung_vergleichbar>",
      "wirklich_einzel_istwerte": "<wirklich_einzel_istwerte>"
    },
    "name": "spuelprogramm_anzeige_istvergleich_extras_und_beladung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_literYesAbgelesener Literwert zum abgeschlossenen Lauf A.
b_literYesEntsprechender Wert B.
gleiche_extrasYesZusatzoptionen bei beiden Läufen bestätigt gleich.
gleiches_programmYesProgramm für beide abgeschlossenen Läufe bestätigt gleich.
wirklich_einzel_istwerteYesBeide Zeilen sind jeweils die Einzelanzeige nach Abschluss.
beladung_und_umgebung_vergleichbarYesMenge, Ausgangslage und beobachtete Umgebung vergleichbar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 safety profile is known and the description is not contradicted. The description adds that only genuinely single post-run display values qualify, which is useful context, but it does not say what happens when a precondition is false (rejection vs. qualified result) or what the reference scale for 'einordnen' is.

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?

It is short and the constraint is placed early, but the German sentence is convoluted and the English half largely repeats it rather than adding information. The bilingual duplication costs space without earning it.

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 six required parameters and no output schema, the description should convey what a caller gets back and how the six confirmations interact. It establishes the comparability framing but leaves the result shape and the consequence of a failed precondition unstated.

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%, so all six parameters are already documented and the baseline is 3. The description reinforces the joint meaning of the four boolean confirmations as prerequisites for comparability, but adds no detail beyond the schema (ranges, units, or what a false boolean implies).

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 the resource (two recorded actual display values from a rinse/wash program) and the condition for handling them, but the operative verb 'einordnen' is abstract and the English gloss only restates it. It never states what the tool actually produces (e.g. a comparability verdict or a normalized comparison), and it does not distinguish itself from the adjacent 'spuelmaschine_beladung_vergleichen' sibling.

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?

It gives an explicit gating condition — use only with comparable program selection and loading — which is genuine when-to-use guidance. But there is no when-not guidance beyond that single constraint, and no named alternative for the case where the two readings are not comparable.

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