Skip to main content
Glama

getecoback-raumklima

miele_gn_packbedarf_drei_teile_aus_bestand

Read-only

Berechne, ob vorhandene passende Teile oder ein dokumentierter Original-GN-Pack die tatsächlich fehlenden drei Rollen abdecken — Compare verified GN pack contents against actual remaining needs

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": {
      "modell_gn_belegt": "<modell_gn_belegt>",
      "gewaehltes_pack": "<gewaehltes_pack>",
      "geplante_beutel": "<geplante_beutel>",
      "geplante_motorschutzfilter": "<geplante_motorschutzfilter>",
      "geplante_abluftfilter": "<geplante_abluftfilter>",
      "beutel_vorhanden": "<beutel_vorhanden>",
      "motorschutz_vorhanden": "<motorschutz_vorhanden>",
      "abluftfilter_vorhanden": "<abluftfilter_vorhanden>"
    },
    "name": "miele_gn_packbedarf_drei_teile_aus_bestand"
  }
}

Input Schema

NameRequiredDescriptionDefault
geplante_beutelYesBeutel bis zum eigenen Planungstermin, aus eigenem belegten Bedarf
gewaehltes_packYesExakt geplanter Herstellerpack
beutel_vorhandenYesBereits vorhandene passende unbenutzte Beutel
modell_gn_belegtYesDeutsches Gerät und GN-Kompatibilität wurden eindeutig belegt
geplante_abluftfilterYesNur tatsächlich benötigte passende AirClean-Abluftfilter im Gitter, ohne HEPA-Kassette
motorschutz_vorhandenYesBereits vorhandene passende Standard-Motorschutzfilter
abluftfilter_vorhandenYesBereits vorhandene passende unverbrauchte AirClean-Abluftfilter im Gitter
geplante_motorschutzfilterYesNachweislich passende zusätzlich benötigte Standard-Motorschutzfilter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the comparison uses verified/documented inputs and actual remaining needs, but it does not disclose what the result looks like, how ambiguity is handled, or any failure conditions.

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

Conciseness4/5

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

The definition is a single front-loaded sentence with the calculation stated first and an English gloss second. It is efficient, though the bilingual duplication and the slight 'Teile' versus 'Rollen' terminology shift use a little extra space.

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?

Eight required parameters are fully documented in the schema, and the read-only annotations cover safety, but there is no output schema. The description does not explain whether the result is a boolean coverage answer, missing counts, or another structure, leaving an important gap for a calculation 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%, including a documented enum for the selected pack. The description does not add parameter-specific meaning, ranges, or constraints beyond what the input schema already provides, so the baseline of 3 is appropriate.

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 specific comparison/calculation: whether existing suitable parts or a documented original GN pack cover the actually missing three rolls. It clearly identifies the resources being compared, but it does not name a sibling tool or explain how this differs from related Miele inventory tools.

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 when-to-use, when-not-to-use, prerequisite, or alternative guidance. The phrase 'Compare verified GN pack contents against actual remaining needs' gives context but does not tell an agent when this tool should be selected over a sibling.

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