Skip to main content
Glama

getecoback-raumklima

backofenauszug_modellbereich_und_betriebsart

Read-only

Bosch HEZ638370 und Miele HFC 72, HFC 70 sowie HFC 70-C anhand der dokumentierten Gerätefamilie abgleichen — Check exact rail families and explicit use exclusions.

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": {
      "auszug": "<auszug>",
      "geraeterahmen": "<geraeterahmen>",
      "pyrolyse": "<pyrolyse>",
      "backwagen": "<backwagen>",
      "bosch_nutzung": "<bosch_nutzung>",
      "exakte_zuordnung": "<exakte_zuordnung>"
    },
    "name": "backofenauszug_modellbereich_und_betriebsart"
  }
}

Input Schema

NameRequiredDescriptionDefault
auszugYesGenaue Zubehörbezeichnung.
pyrolyseYesPyrolysefunktion des konkreten Hauptgeräts.
backwagenYesHat der Bosch-Backofen einen Backwagen?
bosch_nutzungYesVorgesehener Betriebsumfang für Bosch.
geraeterahmenYesBelegte Gerätefamilie des Hauptgeräts.
exakte_zuordnungYesHat der Hersteller die genaue Gerätekennung und dieses Zubehör für den geplanten Einsatz abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover read-only and closed-world behavior, and the description adds that the tool checks exact rail families and explicit use exclusions. However, it does not say what the result looks like, how exclusions are evaluated, or whether documentation is cited.

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 one compact sentence front-loaded with model numbers and followed by the check criterion, with no obvious filler. The mixed German/English phrasing is slightly terse but structurally efficient.

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?

With six required enum parameters and no output schema, the description should explain how the inputs combine and what a result means. It only states the matching basis and exclusions, leaving decision logic and return behavior undocumented.

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 have full schema descriptions and enums, so the schema already carries most parameter meaning. The description names accessory models matching the auszug enum and mentions device family and use exclusions, but adds no detail on pyrolyse, backwagen, bosch_nutzung, or exakte_zuordnung.

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 (abgleichen), concrete resources (Bosch HEZ638370 and Miele HFC 72/70/70-C), and the basis for matching (documented device family). It is clearly a compatibility-matching tool, though it does not distinguish itself from the many sibling backofenauszug checks.

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 phrase 'Check exact rail families and explicit use exclusions' implies the tool is for compatibility and exclusion checks, but it never states when to use this instead of an alternative or what preconditions apply. Usage is only implied.

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