Skip to main content
Glama

getecoback-raumklima

miele_guard_l1_saugpinsel_handgriff_2_0_abnahmebeleg

Read-only

Prüfe, ob das beschriebene Abnehmen des Saugpinsels für das eigene Handgriffmodell belegt ist — Scope detachable dusting brush evidence to the documented Comfort 2.0 handle

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>",
      "griff": "<griff>",
      "pinsel_am_griff_bestaetigt": "<pinsel_am_griff_bestaetigt>",
      "zweck": "<zweck>"
    },
    "name": "miele_guard_l1_saugpinsel_handgriff_2_0_abnahmebeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
griffYesGriff am Gerät exakt identifiziert
zweckYesWelche Nutzung soll geprüft werden
hs22_bestaetigtYesDeutsche Guard L1 Ausführung mit Typ HS22 und zugeordneter Anleitung M.-Nr. 13 114 040 bestätigt
pinsel_am_griff_bestaetigtYesSaugpinsel und auf dem Griff dokumentierte Führung visuell zugeordnet

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 and closed-world scope are covered structurally. The description adds real context by framing the answer as 'belegt' — i.e., only documented configurations count, and an undocumented handle (comfort_ohne_2_0 / unbekannt) presumably yields no evidence. It does not say what the response looks like or how 'offen' inputs are treated, so it remains a modest addition.

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?

The definition is short and front-loaded, leading with the verification question. However, the English clause largely restates the German one rather than adding information, so a meaningful share of the text does not earn its place.

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 convey what a 'Beleg' result looks like (belegt / nicht belegt / offen) and how the required confirmations gate the answer; it does not. It is adequate to identify the tool's subject but thin for a four-required-parameter verification 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 three enums, so the schema already carries the parameter semantics; the baseline of 3 applies. The description echoes 'für das eigene Handgriffmodell' (mapping to 'griff') without adding format, defaults, or interaction rules between 'hs22_bestaetigt' and 'pinsel_am_griff_bestaetigt'.

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 das beschriebene Abnehmen des Saugpinsels ... belegt ist', scoped to a handle model. The English half repeats the same scope ('Scope detachable dusting brush evidence to the documented Comfort 2.0 handle'), so an agent knows this is an evidence-verification check, not an instruction or a lookup of brush compatibility in general. It stops short of naming a sibling it differs from, keeping it at 4.

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 or when-not-to-use guidance, and no alternative tool is named. At best the schema field 'zweck' ('Welche Nutzung soll geprüft werden') implies this is a pre-check before detaching or using the brush on the tube, but that inference is left entirely to the agent.

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