Skip to main content
Glama

getecoback-raumklima

miele_flexiclip_materialnummer_und_ean_widerspruch

Read-only

Bei Miele HFC 70, HFC 70-C und HFC 72 zwei bekannte Kennungen auf Widerspruch prüfen — Detect conflicting material number and barcode evidence on the same accessory.

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": {
      "gleicher_etikettbezug": "<gleicher_etikettbezug>",
      "materialnummer": "<materialnummer>",
      "ean": "<ean>"
    },
    "name": "miele_flexiclip_materialnummer_und_ean_widerspruch"
  }
}

Input Schema

NameRequiredDescriptionDefault
eanYesSichtbare EAN, nur Ziffern, keine Seriennummer. Bei ungeklärter Sicht leer lassen.
materialnummerYesSichtbare Hersteller-Materialnummer, nur Ziffern, keine Seriennummer. Bei ungeklärter Sicht leer lassen.
gleicher_etikettbezugYesSind Materialnummer und EAN nachweislich vom gleichen Etikett oder demselben eindeutig zugeordneten Originalartikel?

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 safety and scope are covered structurally. The description adds the device applicability and the fact that it compares two identifiers, but says nothing about what a conflict verdict looks like, how empty identifiers are treated, or how partial evidence is handled.

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 sentences, with the device scope front-loaded before the action, and no filler. The German/English mirroring is slightly redundant but keeps the definition short and quick to parse.

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 three-parameter check with full schema coverage, the definition is mostly adequate, but with no output schema it leaves the return value (presumably a conflict verdict) entirely unexplained. The interaction between gleicher_etikettbezug and the conflict decision is also not described.

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 three parameters (ean, materialnummer, gleicher_etikettbezug) are already documented with digit-only and empty-if-unclear rules. The description restates the idea of comparing two known identifiers without adding format, precedence, or edge-case meaning beyond the schema.

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 check (conflict detection between material number and barcode) and scopes it to three concrete device models (HFC 70, HFC 70-C, HFC 72), which resolves the cryptic tool name. It does not distinguish the tool from similarly named sibling checks such as miele_flexiclip_simultane_ebenen_paarbedarf or pac_n90_ean_abgleichen.

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?

Applicability is implied through the explicit device scoping (only the three HFC models), which gives an agent a usable condition for selection. There is no statement of when NOT to use it, nor any pointer to the sibling tool that handles the non-conflict or pair-coverage case.

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