Skip to main content
Glama

getecoback-raumklima

ersatzteil_nachfolger_rueckrichtung_passbereich

Read-only

Trenne den belegten Nachfolger eines Ersatzteils von einer nicht belegten Rückrichtung — Check the documented direction of a replacement part succession

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": {
      "artikel_und_geraet_bestaetigt": "<artikel_und_geraet_bestaetigt>",
      "nachfolger_fuer_alt": "<nachfolger_fuer_alt>",
      "alt_fuer_neues_geraet": "<alt_fuer_neues_geraet>",
      "pruefrichtung": "<pruefrichtung>"
    },
    "name": "ersatzteil_nachfolger_rueckrichtung_passbereich"
  }
}

Input Schema

NameRequiredDescriptionDefault
pruefrichtungYesWelche Einbaurichtung wird benötigt?
nachfolger_fuer_altYesHersteller nennt das neue Teil ausdrücklich als Ersatz für eine alte Ausführung
alt_fuer_neues_geraetYesHersteller nennt das alte Teil ausdrücklich für das neuere Gerät
artikel_und_geraet_bestaetigtYesBeide Artikelnummern und die konkrete Gerätevariante sind in der Fundstelle eindeutig

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 by structured data. Beyond that, the description says nothing about what the tool actually does with the three-state enum inputs, what verdict or result it produces, or how conflicts between the two documented directions are resolved. For a decision/validation tool with no output schema, that is a meaningful gap.

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?

A single compact sentence with the core distinction front-loaded, followed by an English gloss. The bilingual duplication is mildly redundant but short enough that nothing is wasted. No filler or hedging.

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 in the schema and the safety profile is in annotations, so the structured data carries most of the burden. However, with no output schema and no statement of what result is returned or how the 'belegt/ausgeschlossen/offen' values combine into a conclusion, the definition is only minimally complete for a decision 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 description coverage is 100% and the three enums carry their own explanations, so the parameters are already well documented. The description's two-direction framing loosely maps onto nachfolger_fuer_alt versus alt_fuer_neues_geraet but adds no format, default, or interaction detail beyond the schema. Baseline 3 is appropriate.

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 specific action (separating the documented successor direction from an undocumented reverse direction) and a concrete resource (replacement-part succession). The English gloss 'Check the documented direction of a replacement part succession' reinforces this. It stops short of differentiating itself from the many other ersatzteil_* siblings, so it is clear but not sibling-aware.

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 use this tool versus the numerous sibling tools, nor any precondition or exclusion. The 'Trenne X von Y' framing hints at the two cases it distinguishes, but that is inferred from the purpose statement rather than stated as usage guidance. An agent must guess at the calling context.

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