Skip to main content
Glama

getecoback-climate-weather

miele_beutelsauger_leistungsverlust_grosse_teile

Read-only

Dokumentiere eine abrupte Veränderung des Saugwegs nach sperrigem Sauggut getrennt von schrittweisem Filterbedarf — Localize a documented onset of restriction after bulky material

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": {
      "beutelmodell_bestaetigt": "<beutelmodell_bestaetigt>",
      "abfall": "<abfall>",
      "sperrgut_vor_abfall": "<sperrgut_vor_abfall>",
      "warmes_gehaeuse": "<warmes_gehaeuse>",
      "sichtbares_hindernis": "<sichtbares_hindernis>"
    },
    "name": "miele_beutelsauger_leistungsverlust_grosse_teile"
  }
}

Input Schema

NameRequiredDescriptionDefault
abfallYesZeitlicher Verlauf aus Beobachtung
warmes_gehaeuseYesUngewöhnlich warmes Gehäuse wurde im selben Vorgang beobachtet
sperrgut_vor_abfallYesUnmittelbar davor wurde sperriges trockenes Sauggut beobachtet
sichtbares_hindernisYesNach Abschalten und Trennen war an einer zulässigen äußeren Verbindung ein Hindernis sichtbar
beutelmodell_bestaetigtYesVorliegendes Miele Beutelgerät eindeutig identifiziert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 the differential framing (abrupt onset after bulky material vs. progressive filter loading), which is genuine context, but says nothing about what gets recorded, whether prior documentation is affected, or what the result looks like.

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?

It is short and front-loads the German statement, but the bilingual restatement consumes roughly half the text without adding new information, and the verb shift ('Dokumentiere'/'Localize') creates noise rather than clarity.

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 five required parameters, four of them enums and one boolean, the tool is structured enough that the schema describes the inputs well. There is no output schema, however, and the description never indicates what a call produces or how the recorded observation is scoped, leaving a gap for a documentation-oriented 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 all five parameters carry individual enum/boolean descriptions, so the schema does the heavy lifting. The description only lightly reinforces 'nach sperrigem Sauggut', which maps to sperrgut_vor_abfall, adding no format or interpretation detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The German half names an action ('Dokumentiere') on a specific subject (abrupt suction-path change after bulky debris), but the English gloss switches to 'Localize', leaving the actual operation ambiguous. The abrupt-vs-stepwise distinction hints at scope, yet an agent cannot confidently separate this from siblings such as miele_beutelsignal_feinstaub_fusseln_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?

'getrennt von schrittweisem Filterbedarf' implies a boundary condition: use when the restriction onset is abrupt rather than gradual. That is useful implied guidance, but no alternative tool is named and no explicit when-not-to-use rule is stated.

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