Skip to main content
Glama

getecoback-climate-weather

dunstabzug_dwb66bc50_normale_maxstufe_kenndaten

Read-only

Rufe die belegten Werte der höchsten Normalstufe nur für die passende DWB66BC50-Konfiguration ab — Retrieve model-specific airflow and sound power for a documented operating mode

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": {
      "de_modell_dwb66bc50": "<de_modell_dwb66bc50>",
      "modus": "<modus>",
      "stufe": "<stufe>",
      "kit_am_geraet_bestaetigt": "<kit_am_geraet_bestaetigt>"
    },
    "name": "dunstabzug_dwb66bc50_normale_maxstufe_kenndaten"
  }
}

Input Schema

NameRequiredDescriptionDefault
modusYesBetriebsart dieser Angabe
stufeYesBezug des verlangten Werts
de_modell_dwb66bc50YesDeutsche Modellkennung und Ausführung des Gerätedatenblatts bestätigt
kit_am_geraet_bestaetigtYesBei Umluft wurde die dazugehörige Clean Air Plus Ausstattung am Gerät bestätigt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and the description only needs to add value. It contributes the notion that only *documented* (belegt) values are returned for this exact model/config, which hints at a fail-closed/empty behaviour, but it never says what is returned or what happens when the config or stufe does not match.

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 front-loaded sentence with the key constraint (model-specific, only the highest normal level) stated first. The German/English duplication and the em-dash aside add mild redundancy but no real noise.

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 form a real precondition chain and there is no output schema, so the description should clarify what is returned and how mismatched configuration or 'andere_stufe'/'unbekannt' are handled. It names the payload (airflow, sound power) but leaves the failure and fallback semantics, and the tension with the broader stufe enum, unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with enum-annotated modus and stufe, so the schema does most of the work. The description still adds meaning by tying retrieval to the DWB66BC50 confirmation flag and to a 'documented operating mode', reinforcing that the booleans act as gates rather than filters.

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?

States a specific verb (abrufen/retrieve) and a specific resource (belegte Werte der höchsten Normalstufe / airflow and sound power) scoped to a named model DWB66BC50. It does not name any sibling tool or explain how it differs from the many other dunstabzug_* lookups, so it stays short of a 5.

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?

'nur für die passende DWB66BC50-Konfiguration' is an implicit precondition that gates when the tool applies, but there is no explicit guidance on when to prefer it over the other attribute-lookup siblings, nor what an agent should do when the configuration does not match.

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