Skip to main content
Glama

getecoback-raumklima

geraetegruppe_zubehoer_symptom_wandert

Read-only

Mit einem bereits dokumentierten freigegebenen Tausch zweier Zubehörteile prüfen, ob ein Befund mit dem Teil oder Gerät verbunden blieb — Classify a recorded cross-swap without assuming it proves a component defect.

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": {
      "a_vorher_auffaellig": "<a_vorher_auffaellig>",
      "b_vorher_auffaellig": "<b_vorher_auffaellig>",
      "a_nachher_auffaellig": "<a_nachher_auffaellig>",
      "b_nachher_auffaellig": "<b_nachher_auffaellig>",
      "vergleich_bestaetigt": "<vergleich_bestaetigt>"
    },
    "name": "geraetegruppe_zubehoer_symptom_wandert"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_vorher_auffaelligYesWar Gerät A ursprünglich mit seinem eigenen Zubehörteil auffällig?
b_vorher_auffaelligYesWar Gerät B ursprünglich mit seinem eigenen Zubehörteil auffällig?
a_nachher_auffaelligYesWar A nach dem dokumentierten Tausch mit dem früheren Teil von B auffällig?
b_nachher_auffaelligYesWar B nach dem dokumentierten Tausch mit dem früheren Teil von A auffällig?
vergleich_bestaetigtYesSind Zubehör für beide Geräte freigegeben, vollständiger Tausch, gleiche Aufgabe und dasselbe Befundkriterium belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 genuine behavioral context beyond that: the operation presupposes a documented approved swap and explicitly cautions that a positive result is not proof of a component defect, which shapes how the agent interprets the outcome. It still does not describe the shape of the classification returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence (given bilingually) that front-loads the required precondition and ends with the key interpretive caveat. No filler, no restatement of the title.

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?

With no output schema, the definition should say what the classification resolves to (symptom follows the part vs. stays with the device). That outcome vocabulary is left implicit, so an agent knows when to call it but not precisely what to expect back.

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%, so all five booleans are already self-explanatory. The description only loosely mirrors the 'vergleich_bestaetigt' precondition (approved accessories, complete swap, same task and criterion) without adding format or edge-case detail 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 names a concrete verb and object: classify a recorded, approved cross-swap of two accessory parts to see whether a symptom stayed with the part or with the device. That is specific enough to distinguish it from the surrounding 'geraetegruppe_*' planning/balancing siblings, though it does not name an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a clear precondition — the swap must already be documented and approved — and adds an interpretive constraint ('without assuming it proves a component defect'). It does not say what to do when no approved swap has been recorded, nor does it point to a sibling tool for that case.

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