Skip to main content
Glama

getecoback-raumklima

dunstabzug_b_label_zwei_unterschiedliche_bezuege

Read-only

Prüfe, auf welche Kennzahl ein beim DWB66BC50 verwendeter Buchstabe tatsächlich bezogen ist — Disambiguate the hood energy, fan, lighting and grease classes

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": {
      "exakt_de_dwb66bc50": "<exakt_de_dwb66bc50>",
      "behaupteter_buchstabe": "<behaupteter_buchstabe>",
      "genannter_bezug": "<genannter_bezug>"
    },
    "name": "dunstabzug_b_label_zwei_unterschiedliche_bezuege"
  }
}

Input Schema

NameRequiredDescriptionDefault
genannter_bezugYesDer Buchstabe wird in der vorliegenden Aussage für Folgendes verwendet
exakt_de_dwb66bc50YesDeutsche DWB66BC50-Dokumentation gehört zur betrachteten Haube
behaupteter_buchstabeYesAbgelesener Buchstabe

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 adds the disambiguation scope across four classes but says nothing about how the verdict is derived or what the caller receives, so behavioral value beyond annotations is modest.

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?

Purpose is front-loaded in the first clause, with a compact English gloss that usefully names the four class families. No wasted preamble; the bilingual duplication is justified because the gloss adds the class list.

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 small read-only three-parameter check the description covers intent, but with no output schema it leaves the result of the check (a verdict? a corrected reference?) unstated, so an agent cannot fully anticipate the response.

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% with two enums, so the schema carries the parameter burden and baseline 3 applies. The description's list of energy/fan/lighting/grease classes loosely maps to the 'genannter_bezug' enum but adds no format or edge-case guidance (e.g. what 'offen' means).

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?

Names a specific verb ('Prüfe') and a precise subject: which metric (Kennzahl) a letter on the DWB66BC50 actually refers to, and the English tagline narrows it to the energy, fan, lighting and grease classes. That is enough to separate it from sibling measurement/label tools, though it never names an alternative tool outright.

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?

The wording implies the usage context (a letter's reference is ambiguous and needs disambiguating), but there is no explicit when-to-use/when-not or routing to any sibling such as the DWB66BC50 Kenndaten tool. Usage is inferable rather than 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