Skip to main content
Glama

getecoback-climate-weather

miele_boost_cx1_maxmarkierung_behaelter

Read-only

Lies die direkte Max-Markierung des belegten Boost-CX1-Behälters statt einer Wechselanzeige für Beutel — Inspect the documented bagless container fill line

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": {
      "cx1_bestaetigt": "<cx1_bestaetigt>",
      "markierung_sichtbar": "<markierung_sichtbar>",
      "fuellstand": "<fuellstand>",
      "nur_aus_saugleistung_vermutet": "<nur_aus_saugleistung_vermutet>"
    },
    "name": "miele_boost_cx1_maxmarkierung_behaelter"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuellstandYesDirekt bei abgeschaltetem Gerät aufgezeichneter Vergleich
cx1_bestaetigtYesDeutsche Boost CX1 Cat & Dog PowerLine-Ausführung 11602420 und zugeordnete Anleitung bestätigt
markierung_sichtbarYesMax-Markierung am eigenen Staubbehälter war eindeutig zu sehen
nur_aus_saugleistung_vermutetYesEs liegt nur die Vermutung aus schwächerer Saugleistung vor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that this is a read-only, closed-world tool. The description adds useful semantic context by clarifying that it reads the direct marking rather than relying on a bag-change signal, but it does not describe the inspection process, interpretation of enum outcomes, or any further behavioral constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no filler. The German statement is concise, and the English clause clarifies the technical meaning without adding unnecessary length.

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 read-only inspection tool with four fully described parameters and no output schema, the description is largely complete. It clearly states the inspection target and rejects a common alternative interpretation, though it could do slightly more to explain when an agent should choose this tool over related inspection tools.

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 four parameters are already well documented, including the two enum fields. The description adds conceptual context about direct marking versus inferred suction performance, but it does not provide additional parameter-level guidance beyond the schema.

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

Purpose5/5

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

The description states a specific read action on a specific resource: the direct Max marking of the loaded Boost-CX1 container. It also explicitly contrasts this with a bag-change indicator, which prevents confusion with bag-based fill indicators.

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?

The description implies the tool is for inspecting the documented bagless container fill line and says it is used instead of a bag-change indicator. However, it does not explicitly define when to use this tool versus alternatives, nor does it name or distinguish among sibling tools.

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