Skip to main content
Glama

getecoback-climate-weather

miele_guard_l1_beutelanzeige_pruefbedingungen

Read-only

Prüfe, ob die protokollierte Ablesung der Beutelanzeige unter den vorgesehenen Bedingungen stattfand — Confirm the observed Guard L1 bag-indicator measurement setup

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": {
      "hs22_bestaetigt": "<hs22_bestaetigt>",
      "umschaltbare_bodenduese": "<umschaltbare_bodenduese>",
      "maximale_stufe_belegt": "<maximale_stufe_belegt>",
      "duese_abgehoben": "<duese_abgehoben>",
      "ablesung": "<ablesung>"
    },
    "name": "miele_guard_l1_beutelanzeige_pruefbedingungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
ablesungYesBeobachteter Anzeigestatus
duese_abgehobenYesDüse war bei der Ablesung ein Stück vom Boden abgehoben
hs22_bestaetigtYesDeutsche Guard L1 Ausführung mit Typ HS22 und zugeordneter Anleitung M.-Nr. 13 114 040 bestätigt
maximale_stufe_belegtYesMaximale Saugstufe wurde bei der Ablesung eindeutig eingestellt
umschaltbare_bodendueseYesUmschaltbare Bodendüse des vorgesehenen Prüfschritts eingesetzt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety is covered. The description adds that this is a conditions-verification step, but never says what a negative result looks like (error vs. verdict), nor whether the check is authoritative for downstream decisions — meaningful gaps for an evaluation tool.

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?

Two short clauses front-loaded with the verb, but the German and English halves are near-duplicates rather than complementary, so roughly half the text does not add information. Efficient in length, wasteful in redundancy.

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 should indicate what a confirmation yields (a boolean verdict, a pass/fail with reasons, an exception). It does not, leaving the return contract undefined for a five-required-parameter check tool.

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 five fully documented, enum-constrained required parameters, so the schema carries the semantics. The description adds no parameter-level meaning beyond that baseline, which is exactly a 3.

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 and resource: "Prüfe, ob die protokollierte Ablesung der Beutelanzeige ... stattfand" — a validation check on a recorded bag-indicator reading. The English half ("Confirm the observed ... measurement setup") is vaguer and largely restates the German, but an agent can still tell this is a precondition-verification tool rather than a reset or lookup.

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?

No explicit when-to-use guidance, no prerequisites, and no mention of any alternative or sibling tool. The phrase "unter den vorgesehenen Bedingungen" hints that this gates interpretation of a reading, but the agent must infer that purpose entirely on its own.

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