Skip to main content
Glama

getecoback-raumklima

dunstabzug_gehaeusehoehe_je_betriebsbauform

Read-only

Vergleiche den dokumentierten Gehäuseraum der genauen DWB66BC50-Variante mit der eigenen Bezugshöhe — Compare the hood outline height for the documented configuration

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>",
      "umhuellung": "<umhuellung>",
      "freie_hoehe_mm": "<freie_hoehe_mm>",
      "gleicher_bezug": "<gleicher_bezug>"
    },
    "name": "dunstabzug_gehaeusehoehe_je_betriebsbauform"
  }
}

Input Schema

NameRequiredDescriptionDefault
umhuellungYesExplizit dokumentierte Zeile der Maßzeichnung
freie_hoehe_mmYesVerfügbare freie Höhe am gleichen oberen und unteren Gehäusebezug wie in der gewählten Zeile
gleicher_bezugYesMaßrichtung, Gehäusegrenzen und Konfiguration eindeutig zugeordnet
de_modell_dwb66bc50YesDeutsche Modellkennung entspricht dem verwendeten Datenblatt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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. Beyond that the description says nothing new: it does not explain what the comparison yields (a verdict, a delta, a boolean?), how mismatched reference frames are handled, or what happens when gleicher_bezug is false. For a tool with no output schema, that is a real gap.

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?

A single sentence with no padding, but the bilingual rendering is not a faithful restatement and creates ambiguity rather than reinforcement. The key constraint (compare documented vs. own reference height) is present but under-specified rather than front-loaded with actionable detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four required parameters, no output schema, and the description never says what comes back or how the comparison is expressed. For a comparison/verification tool the agent needs to know the result shape and the consequence of each umhuellung option; neither is covered.

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, including the umhuellung enum, is documented in the schema itself, so the baseline is 3. The description loosely ties de_modell_dwb66bc50 to "der genauen DWB66BC50-Variante" and freie_hoehe_mm/gleicher_bezug to "eigene Bezugshöhe," but adds no format, tolerance, or enumeration meaning beyond the schema.

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 verb ("Vergleiche/Compare") and subject ("Gehäuseraum der genauen DWB66BC50-Variante") are stated, but the English half shifts to "hood outline height for the documented configuration," which is not the same thing as comparing against the user's own reference height. The two language versions do not describe an identical operation, and nothing distinguishes this from closely named siblings such as dunstabzug_dwb66bc50_normale_maxstufe_kenndaten or dunstabzug_b_label_zwei_unterschiedliche_bezuege.

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 statement, no when-not-to-use, and no named alternative among the many dunstabzug siblings. The phrase "mit der eigenen Bezugshöhe" hints that this is a fit/compatibility check, but the agent is left to infer that from the wording alone.

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