Skip to main content
Glama

getecoback-raumklima

ersatzteil_fachangebot_diagnose_gleichnamiger_fehler

Read-only

Ein zugeordnetes Ersatzteil vom Verkaufsvorschlag unterscheiden, wenn dieselbe Fehlermeldung mehrere Ursachen haben kann — Check whether the quoted part follows the confirmed diagnosis for this case.

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": {
      "meldung_zum_modell": "<meldung_zum_modell>",
      "fachdiagnose": "<fachdiagnose>",
      "angebot_match": "<angebot_match>"
    },
    "name": "ersatzteil_fachangebot_diagnose_gleichnamiger_fehler"
  }
}

Input Schema

NameRequiredDescriptionDefault
fachdiagnoseYesBefund zur Teileursache für genau dieses Gerät.
angebot_matchYesDie Werkstatt ordnet dieselbe exakte Teilenummer dem bestätigten Befund ausdrücklich zu?
meldung_zum_modellYesDie Fehlermeldung wurde im genauen Modellkontext dokumentiert?

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 behavior is covered. The description adds the diagnostic rationale (distinguishing quote from confirmed diagnosis under ambiguous error causes) but never states what the call produces — a verdict, a classification, or a confirmation — leaving the result shape opaque for a decision-style tool.

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?

Two compact sentences with the constraint front-loaded and no filler. The English half largely restates the German, but it does decode the dense compound 'Fachangebot' into plainer phrasing, so the duplication is only mildly wasteful.

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 three required parameters are covered by schema descriptions and the read-only nature is annotated, so the calling contract is adequate. With no output schema, though, the description should have explained what determination comes back for a tool whose entire point is producing a judgment; that omission leaves a real gap.

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 the parameters are already fully documented, and the enum on fachdiagnose is self-explanatory from the schema. The description adds only a light relational hint — that the quoted part is compared against the confirmed diagnosis — without explaining how fachdiagnose values like 'mehrere_moeglich' or 'anderes_teil' should be combined with angebot_match.

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 operation on a concrete resource: separating an assigned spare part from the sales suggestion, and checking whether the quoted part follows the confirmed diagnosis. The qualifying condition (identical error message with multiple possible causes) makes the intent recognizable. It does not, however, differentiate itself from the many similarly named ersatzteil_* siblings.

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?

Usage is implied by the clause 'wenn dieselbe Fehlermeldung mehrere Ursachen haben kann', which tells the agent the ambiguity precondition for calling it. There is no explicit when-not guidance and no routing to any of the ~30 sibling tools that sound near-identical, so the agent must infer the boundary itself.

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