Skip to main content
Glama

getecoback-raumklima

miele_hyclean_beutel_vollstaendige_modellzeile

Read-only

Lies die eindeutige Classic-, Complete-, Compact- oder Guard-Bezeichnung ab und prüfe den vorgesehenen Beuteltyp — Match an exact German Miele vacuum model to its documented bag family

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": {
      "modellfamilie": "<modellfamilie>",
      "beutel_am_angebot": "<beutel_am_angebot>"
    },
    "name": "miele_hyclean_beutel_vollstaendige_modellzeile"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellfamilieYesVollständige deutsche Modellbezeichnung auf Typenschild oder Anleitung
beutel_am_angebotYesSichtbarer Typ auf der konkreten Packung oder im Angebot

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 clear and the description need not restate it. What the description does not disclose is the outcome semantics: whether a mismatch returns false, an error, or a corrective hint, and how 'unbekannt' inputs are treated. For a read-only lookup this is a moderate rather than serious gap.

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 core statement is front-loaded and easy to parse, but the definition says the same thing twice – once in German and again in English – so roughly half the text is duplicated rather than additive. The bilingual duplication costs space without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, fully enumerated, read-only lookup with no output schema, this is close to sufficient: the agent knows what inputs to supply and what question is being answered. The remaining gap is that nothing indicates the shape of the verdict (match vs. mismatch vs. unknown), which matters for a comparison 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% and both parameters are fully enumerated, so the schema carries most of the weight and a 3 is the baseline. The description does add a small amount of meaning by naming the four model families and by tying the bag parameter to what is printed on the pack/offer, but it does not explain how the two enums are reconciled or what a valid pairing looks like.

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 states a concrete action pair – read the Classic/Complete/Compact/Guard designation and check the intended bag type against it – which is a specific verb plus a specific resource (German Miele model -> documented bag family). It is clear what the tool resolves, though it never contrasts itself with the many sibling bag/model tools in the catalog.

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?

Usage is only implied: the agent must already have a full German model designation and a bag type visible on packaging to call it. There is no explicit when-to-use statement, no exclusion of alternatives such as the model-family or bag-signal sibling tools, and no mention of when the 'unbekannt' enum value should be chosen.

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