Skip to main content
Glama

getecoback-raumklima

brita_anzeigedeckel_getauscht_nutzungszaehler_zuordnung

Read-only

Nach Tausch zweier Kannen-Deckel prüfen, ob eine Anzeige noch der richtigen Kartusche zugeordnet ist — Keep paired indicator history separate from vessel identity.

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": {
      "beide_kannen_identifiziert": "<beide_kannen_identifiziert>",
      "deckelwechsel": "<deckelwechsel>",
      "kartusche_mit_deckel": "<kartusche_mit_deckel>",
      "neuansatz_bestaetigt": "<neuansatz_bestaetigt>"
    },
    "name": "brita_anzeigedeckel_getauscht_nutzungszaehler_zuordnung"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckelwechselYesBeobachtete Übergabe des Deckels.
kartusche_mit_deckelYesGehört die aktuelle Kartusche anhand des dokumentierten Verlaufs genau zu dem mitgewechselten oder vorhandenen Deckel?
neuansatz_bestaetigtYesIst belegt, dass die aktuelle Anzeige erst bei der ersten Nutzung dieser konkreten neuen Kartusche angesetzt wurde?
beide_kannen_identifiziertYesSind zwei einzelne Kannen, Kartuschen und Anzeigedeckel im Protokoll eindeutig bezeichnet?

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 the safety profile is covered by structured data. The description adds a genuine interpretive principle — keep paired indicator history separate from vessel identity — which is real value beyond the annotations, but it says nothing about what the check returns or how a partial/ambiguous state is reported.

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 compact clauses, with the precondition front-loaded before the check itself. The mixed German/English phrasing is slightly redundant but the second clause adds a distinct interpretation rule rather than repeating the first, so little is wasted.

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?

For a read-only, no-output-schema tool with four fully documented required parameters, this covers the essentials. The notable gap is that, with no output schema, the description does not indicate what verdict or fields come back — which matters for a tool whose whole purpose is producing a consistency judgement.

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%, including enum value descriptions for deckelwechsel and kartusche_mit_deckel, so the schema carries the parameter burden. The description only restates the core concept (Deckel-Tausch, Anzeige-zu-Kartusche-Zuordnung) without adding format 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?

States a specific verb (prüfen) and a specific object (ob eine Anzeige noch der richtigen Kartusche zugeordnet ist) under a stated precondition (nach Tausch zweier Kannen-Deckel). An agent can tell this is a verification/consistency-check tool rather than a mutation. It does not name or distinguish any sibling, so it stops short of a 5.

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?

The trigger is implied clearly enough — use it after a lid swap between two jugs — but there is no explicit when-not guidance and no named alternative among the many brita_* siblings. The presence of 'kein_wechsel' in the schema also slightly undercuts the 'after a swap' framing, since the tool apparently also handles the no-swap case, and the description does not reconcile that.

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