Skip to main content
Glama

getecoback-raumklima

backofenauszug_auflageart_baugruppe_und_abmessungsbeleg

Read-only

Die veröffentlichte Auflageart eines Auszugs mit einem tatsächlich geprüften Blech oder Rost abgleichen — Separate documented tray categories from fit of one particular item.

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>",
      "auflage": "<auflage>",
      "auszug_geraet_belegt": "<auszug_geraet_belegt>",
      "auflage_exakt": "<auflage_exakt>"
    },
    "name": "backofenauszug_auflageart_baugruppe_und_abmessungsbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
auszugYesGewählter genau identifizierter Vollauszug.
auflageYesTatsächlich gewünschter aufliegender Gegenstand.
auflage_exaktYesIst das genaue Blech, der genaue Rost oder die genaue Auflage laut Geräteunterlagen für diesen Gebrauch bestätigt?
auszug_geraet_belegtYesIst der Auszug für das konkrete Hauptgerät nachvollziehbar zugeordnet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that this is a comparison between documented categories and an actual checked item, but it does not explain how mismatches are reported, what the result looks like, or any other behavioral detail beyond the annotations.

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 description is two focused sentences with no filler. The first sentence front-loads the comparison action, and the second clarifies the documented-versus-actual distinction, though the phrasing remains somewhat abstract.

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?

All four required parameters are fully documented and the tool is read-only, but with no output schema the description should clarify what a successful comparison returns or how mismatches are represented. It leaves the result semantics unspecified for a validation-style tool.

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 coverage is 100%, with clear enum descriptions for all four parameters. The description reinforces the distinction between 'veröffentlichte Auflageart' and 'tatsächlich geprüften Blech oder Rost', but it does not add format, interpretation, or interaction details beyond the schema.

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 states a specific action ('abgleichen') and two concrete resources: the published Auflageart of a pull-out and an actually checked tray or grate. The contrast between documented tray categories and fit of a particular item further clarifies intent, though no sibling tool is named.

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 guidance, no prerequisites, and no named alternatives. The phrase 'Separate documented tray categories from fit of one particular item' implies a reconciliation context but does not tell an agent when to choose this tool over the many sibling backofenauszug tools.

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