Skip to main content
Glama

getecoback-climate-weather

miele_flexiclip_simultane_ebenen_paarbedarf

Read-only

Bereits vollständige passende Paare erst gegen wirklich gleichzeitig benötigte Auflageebenen rechnen — Count how many complete single-pair boxes remain needed.

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": {
      "auszug": "<auszug>",
      "zuordnung_gleichzeitig": "<zuordnung_gleichzeitig>",
      "benoetigte_ebenen": "<benoetigte_ebenen>",
      "bestaetigte_paare": "<bestaetigte_paare>",
      "angekuendigte_paare": "<angekuendigte_paare>"
    },
    "name": "miele_flexiclip_simultane_ebenen_paarbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
auszugYesGenau belegter Miele FlexiClip Typ.
benoetigte_ebenenYesAnzahl der Ebenen, die im eigenen Ablauf gleichzeitig einen Auszug brauchen.
bestaetigte_paareYesBereits vollständige passende Paare außerhalb der noch nicht bestätigten Beigaben.
angekuendigte_paareYesZusätzlich zugesagte, aber am konkreten Gerät oder Paket noch nicht bestätigte Paare.
zuordnung_gleichzeitigYesSind die konkreten Ebenen und die gewünschte gleichzeitige Ausstattung für Gerät und Zubehör nach Unterlagen geprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 covered. The description adds one behavioral nuance beyond that: only levels that are 'wirklich gleichzeitig' required count toward the calculation. It does not describe the returned figure, rounding, or what happens when angekuendigte_paare exceed benötigte_ebenen.

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 a single sentence with the operative constraint front-loaded, which is good. However, the German clause and the English gloss largely restate each other, and neither pins down the output, so the words spent on duplication do not fully earn their place.

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 five-required-parameter calculation tool with no output schema, an agent still lacks the return shape (a single count? a breakdown?) and any edge-case behavior. The description conveys the general intent but leaves the result underspecified relative to the tool's parameter complexity.

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 five parameters, including the enum for Auszug and the boolean zuordnung_gleichzeitig, are already documented inline. The description adds no meaning about how the numbers combine (e.g., whether confirmed and announced pairs are summed or subtracted from the level requirement), so the baseline 3 applies.

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 concrete computation (rechnen/count) over a concrete resource (vollständige passende Paare vs. gleichzeitig benötigte Auflageebenen) and states the result — how many complete single-pair boxes remain needed. It does not differentiate itself from any sibling, and the German clause is jargon-heavy enough to require careful parsing.

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 explicit guidance on when to call this versus alternatives such as flexiclip_ein_paar_zwei_kalte_zeitfenster or miele_flexiclip_materialnummer_und_ean_widerspruch. The word 'erst' hints at a sequencing intent (settle confirmed pairs before computing), but no when-not condition or prerequisite check 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