Skip to main content
Glama

getecoback-raumklima

stapelsaeule_einzelgeraetwechsel_alter_satz_neuer_beleg

Read-only

Bei Austausch nur eines Geräts die frühere Kombination von der neuen Herstellerzuordnung trennen — Recheck a retained kit when one of the two appliances changes.

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": {
      "satz": "<satz>",
      "wechsel": "<wechsel>",
      "bisherige_zuordnung": "<bisherige_zuordnung>",
      "neue_zuordnung": "<neue_zuordnung>",
      "weiterverwendung_satz": "<weiterverwendung_satz>"
    },
    "name": "stapelsaeule_einzelgeraetwechsel_alter_satz_neuer_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
satzYesExakt gekennzeichneter bisheriger Verbindungssatz.
wechselYesWas ändert sich laut der geplanten neuen Kombination?
neue_zuordnungYesUnabhängig abgeglichener Herstellerbeleg für genau das neue Gerätepaar und diesen Satz.
bisherige_zuordnungYesHerstellerbeleg für die bisherige Paarung.
weiterverwendung_satzYesWiederverwendbarkeit nach Herstellerunterlagen und für das tatsächliche Teil geprüft.

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 the safety profile is covered. The description adds the conceptual operation (detaching the old pairing, rechecking the retained kit) but says nothing about what the call produces, how conflicting enum values (e.g. 'abweichend') are handled, or whether the check is advisory. That is meaningful context beyond the annotations but incomplete.

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 two-part sentence with the trigger condition front-loaded and no filler. The bilingual duplication is slightly redundant but serves clarity in a jargon-heavy domain.

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?

For a read-only, closed-world classification tool with five fully documented required enum parameters, the description covers the 'what and when'. With no output schema, though, it should hint at what the verdict/record looks like, and it leaves ambiguity around how the three-state assignment fields combine into an outcome.

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 all five parameters carry enums with their own descriptions ('bestaetigt/abweichend/offen' semantics are spelled out per field). The description adds no additional meaning about any parameter, so the baseline of 3 applies.

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 operation: when only one appliance is swapped, separate the earlier pairing ('frühere Kombination') from the new manufacturer assignment and recheck a retained kit. This is clearly distinguishable from a sibling like wasch_trocken_saeule_herstellerkombination_beleg or stapelsaeule_auszugsnutzen_zwei_getrennte_arbeitsproben. However, the dense bilingual jargon and the missing title keep it from being instantly unambiguous.

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?

The trigger condition is given explicitly ('Bei Austausch nur eines Geräts' / 'when one of the two appliances changes'), which is a clear context. But there is no indication of when NOT to use it or which sibling to prefer for the two-appliance or full-kit case, so the agent must infer the routing.

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