Skip to main content
Glama

getecoback-raumklima

backofenzubehoer_reinigungsart_exakter_beleg

Read-only

Pyrolyse- und Spülmaschinenbelege für genaues Zubehör vom Merkmal des Backofens trennen — Evaluate the requested cleaning method from its actual scope.

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": {
      "geraet": "<geraet>",
      "teil": "<teil>",
      "verfahren": "<verfahren>",
      "teil_zum_geraet_belegt": "<teil_zum_geraet_belegt>",
      "anleitungsbefund": "<anleitungsbefund>"
    },
    "name": "backofenzubehoer_reinigungsart_exakter_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
teilYesEindeutig identifiziertes Teil.
geraetYesExakt bestätigtes Hauptgerät oder passender Herstellerbereich.
verfahrenYesNachzulesende Reinigungsart.
anleitungsbefundYesZusätzlicher eindeutiger Herstellerbeleg für genau diese Geräte-Teil-Methoden-Kombination. Offen, wenn nur das Gerät eine Reinigungsfunktion nennt.
teil_zum_geraet_belegtYesIst für genau dieses Gerät und Teil die Herstellerzuordnung bestätigt?

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. The description adds nothing behavioral beyond that: it does not say what the evaluation produces, how "offen" differs from "abweichend" in outcome, or what the caller learns from a passing vs. failing check. With annotations present the bar is lower, but this text contributes no extra context at all.

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?

It is a single short sentence with no filler, which is good. However brevity here comes at the cost of clarity: the mixed-language clause and the competing verbs make the sentence harder to read than a plain longer statement would be.

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?

This is a five-required-parameter decision tool with no output schema, so the description must explain what the caller gets back and how to interpret a confirmed/divergent/open result. It does neither. The agent knows the topic but not the contract, which is a significant gap for a tool whose entire value is the verdict it returns.

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 four of five parameters are enums with their own descriptions, so the schema fully carries parameter meaning. The description mentions the cleaning method and the oven attribute but adds no interpretation of the enum values or of how teil_zum_geraet_belegt interacts with anleitungsbefund. Baseline 3 applies when the schema does the work.

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 sentence names the domain concretely (Pyrolyse- und Spülmaschinenbelege, Zubehör, Backofen) and gestures at a verb ("trennen"), so an agent knows the topic area. But the two halves conflict: one says the tool separates records/evidence, the other says it evaluates a requested cleaning method against its actual scope. The agent cannot tell whether the tool classifies, splits, or confirms, and the German/English mix makes the operation harder to parse than the name alone.

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 statement of when to call this tool versus the many sibling *_beleg tools (e.g. backofenzubehoer_nur_ersetzen_wenn_funktion_fehlt or kontaktgrill_platten_spuelmaschine_beleg). The only implied guidance is the topic itself. No preconditions, no exclusions, no alternatives are named.

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