Skip to main content
Glama

getecoback-raumklima

geraet_zubehoer_beim_wechsel_getrennt_verplanen

Read-only

Noch benötigtes und belegbar übernehmbares Zubehör beim Gerätewechsel getrennt zählen — Keep a working fallback equipped while transferring verified spares.

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": {
      "wechsel_passung_belegt": "<wechsel_passung_belegt>",
      "einsatzbereit": "<einsatzbereit>",
      "beim_altgeraet": "<beim_altgeraet>",
      "beim_zielgeraet": "<beim_zielgeraet>",
      "ziel_hat_bereits": "<ziel_hat_bereits>"
    },
    "name": "geraet_zubehoer_beim_wechsel_getrennt_verplanen"
  }
}

Input Schema

NameRequiredDescriptionDefault
einsatzbereitYesNutzbare geeignete Teile des betrachteten Typs.
beim_altgeraetYesMindestzahl, die bis zur bestätigten Umstellung am bisherigen Gerät bleiben soll.
beim_zielgeraetYesZahl der für den Start am Zielgerät notwendigen Teile.
ziel_hat_bereitsYesZusätzliche bereits vorhandene bestätigte Teile am Zielgerät.
wechsel_passung_belegtYesSind Zustand und Übernahme der gleichartigen Zubehörteile für beide Geräte belegt?

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 and the burden on the description is lower. Beyond that, the description adds only the vague notions of 'belegbar' and 'fallback' without saying how the boolean gate affects the result, whether counts are clamped, or what the response contains — and with no output schema, the description is the only place that could explain the return value.

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 compact sentence-pair with no filler, but the bilingual duplication is not a translation — the English clause introduces a different idea (fallback provisioning), which creates ambiguity rather than reinforcement. The core operation is not front-loaded in a way an agent can act on quickly.

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-parameter, all-required, closed-world computation with no output schema, so the description should say what the tool returns (a count split? a feasibility verdict?) and how the verification boolean changes the answer. It does neither, leaving the agent unable to predict the result of a call it is otherwise able to construct.

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% with five required numeric/boolean parameters each documented, so the schema carries parameter meaning. The description adds nothing parameter-specific — it does not link 'getrennt zählen' to the altgeraet/zielgeraet split or explain the role of wechsel_passung_belegt as a gate. Baseline 3 applies.

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 German half names a concrete action (separately counting still-needed vs. verifiably transferable accessories during a device swap), but the English half ("Keep a working fallback equipped while transferring verified spares") drifts into advice rather than restating the operation. An agent gets the general domain but not a crisp statement of what is computed or returned, and nothing distinguishes it from siblings such as spuelmaschine_zubehoer_korb_umbauwechsel.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites (e.g., that wechsel_passung_belegt must be confirmed first), and no named alternative among the many geraet_* siblings. The only implied usage signal is the phrase 'beim Gerätewechsel' inside the purpose sentence.

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