Skip to main content
Glama

getecoback-raumklima

wasch_trocken_saeule_herstellerkombination_beleg

Read-only

Dokumentierte Miele-Baureihen und Bosch WQG241001 Bedingungen nach Verbindungssatz prüfen — Verify the exact published scope and exceptions of a stacking kit.

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": {
      "satz": "<satz>",
      "trockner": "<trockner>",
      "waesche_modell": "<waesche_modell>",
      "miele_blende": "<miele_blende>",
      "bosch_waschmaschine": "<bosch_waschmaschine>",
      "podest": "<podest>"
    },
    "name": "wasch_trocken_saeule_herstellerkombination_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
satzYesExakt gekennzeichneter Verbindungssatz.
podestYesWird für die Bosch-Säule ein Podest eingeplant?
trocknerYesAm konkreten Trockner bestätigte Variante.
miele_blendeYesBlendenform laut Unterlagen, soweit für WTV 501 relevant.
waesche_modellYesAm unteren Gerät bestätigte Geräteart oder Baureihe.
bosch_waschmaschineYesBei WQG241001: exakte Bosch-Waschmaschine als geeignet bestätigt, gleiche Breite und Tiefe jeweils mit gleicher Maßbasis sowie Arbeitsplattentiefe >550 mm. Bei anderer Marke offen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 usefully signals that the answer is grounded in published documentation ('exact published scope and exceptions'), which tells the agent to expect a rule-based verdict rather than a general opinion. However, it says nothing about what the response contains (verdict vs. list of exceptions), or how 'offen' inputs are handled.

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?

A single compact sentence in German with a parallel English rendering; nothing is padded. The bilingual duplication is redundant for a single-language agent but cheap, and the verification intent is front-loaded.

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 six-parameter, all-required read-only verification tool with no output schema, the definition should clarify the shape of the expected result (permitted/not permitted plus which exception applies) and the meaning of the 'offen' enum values. The fully documented schema partially compensates, but the description leaves the outcome semantics underspecified.

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?

All six parameters are required, fully enumerated, and carry 100% schema description coverage, so the schema already carries the semantics. The description adds no parameter-level detail beyond naming the Miele series and the Bosch WQG241001 case, which the schema itself already states in more depth (width/depth/worktop >550 mm). 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 verb ('prüfen'/'verify') and a concrete resource ('den dokumentierten Umfang und die Ausnahmen eines Verbindungssatzes'), and it pins down the entities involved: Miele series and Bosch WQG241001. It is not a tautology of the tool name. It stops short of distinguishing itself from close siblings such as stapelsatz_typenschild_artikelnummer_beleg or stapelsaeule_einzelgeraetwechsel_alter_satz_neuer_beleg.

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?

Usage is only implied: an agent can infer the tool is used to check whether a specific stacking-kit/device combination is within the published scope. There is no explicit 'use this when…' statement, no exclusion, and no named alternative for adjacent checks (e.g. height balance or stacking versus side-by-side).

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