Skip to main content
Glama

getecoback-climate-weather

miele_guard_l1_parksystem_pause_oder_aufbewahrung

Read-only

Prüfe bei dem dokumentierten Guard, ob die gewählte Parkposition für eine kurze Pause oder die Abstellung vorgesehen ist — Match the documented HS22 parking position to the intended use

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>",
      "zweck": "<zweck>",
      "flaeche": "<flaeche>",
      "parkaufnahme": "<parkaufnahme>"
    },
    "name": "miele_guard_l1_parksystem_pause_oder_aufbewahrung"
  }
}

Input Schema

NameRequiredDescriptionDefault
zweckYesEigene Absicht
flaecheYesBeobachtete Lage des vorgesehenen Platzes
parkaufnahmeYesIdentifizierte Aufnahme laut Abbildung
hs22_bestaetigtYesDeutsche Guard L1 Ausführung mit Typ HS22 und zugeordneter Anleitung M.-Nr. 13 114 040 bestätigt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description need only add beyond that. It does add the precondition of a documented Guard with the matching manual (M.-Nr. 13 114 040 appears only in the schema), but it never says what the tool returns for a pause-vs-storage determination, which matters since no output schema exists.

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 description is short, but it spends its length on the same sentence twice in two languages, and the second rendering is the vaguer of the two. Nothing is front-loaded as a decision rule; the reader has to reconcile the German and English halves.

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?

Four required parameters are fully documented in the schema and the read-only annotation removes the biggest risk, so the essentials for calling correctly are present. What is missing is the decision logic: how a pause mount versus an underside mount should be reported for a given zweck, and the shape of the result.

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 every parameter carries its own description plus enums for three of four, so the schema does the work. The description adds no mapping between the observed flaeche/parkaufnahme values and the zweck decision, which is the one piece of semantics that would have merited above baseline.

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 clause names a verb ("Prüfe") and a resource ("gewählte Parkposition") and frames the check as pause-vs-storage, so the intent is recoverable. But the English half ("Match the documented HS22 parking position to the intended use") introduces HS22, which the German half omits, and the two halves read as loosely parallel rather than as one precise statement of what the tool decides.

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 when-to-use/when-not guidance and no reference to any alternative tool, despite a large sibling catalog containing several pause/aufbewahrung tools. The only contextual cue is the implicit precondition that the unit be a documented HS22 Guard L1, which is a condition for calling it, not guidance about choosing it.

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