Skip to main content
Glama

getecoback-raumklima

ersatzteil_erneuerung_passung_und_einsatzzeit

Read-only

Vergleichen, ob ein altes Gerät mit einem bestätigten Ersatzteil früher wieder nutzbar wäre als der bereits geprüfte Ersatz — Compare repair-part lead time and setup time with a confirmed replacement path.

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": {
      "teil_tage": "<teil_tage>",
      "einbau_tage": "<einbau_tage>",
      "ersatz_bereit_tage": "<ersatz_bereit_tage>",
      "wechsel_belegt": "<wechsel_belegt>"
    },
    "name": "ersatzteil_erneuerung_passung_und_einsatzzeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
teil_tageYesBestätigte Lieferzeit des exakt passenden Ersatzteils.
einbau_tageYesZusätzliche Zeit im Reparaturangebot bis zur Nutzbarkeit.
wechsel_belegtYesPassung, Umsetzbarkeit und Termin der Reparatur für das konkrete Gerät wurden geprüft?
ersatz_bereit_tageYesBestätigte Zeit bis zum einsatzbereiten Ersatzgerät.

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 safe, closed-world nature is known. The description adds that the comparison relies on confirmed data ('bestätigten', 'bereits geprüften'), which is useful context, but it says nothing about the return value, determinism, or what the comparison produces. With annotations covering the safety profile, a 3 is appropriate.

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?

The description is a single front-loaded sentence that gets to the comparison immediately. The German text is followed by an English translation, which is slightly redundant but not verbose; every clause carries the core comparison idea.

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 comparison tool with four fully documented parameters and no output schema, the main missing piece is a description of what the tool returns (e.g., which option is faster or by how much). Without that, an agent knows how to call it but not what result to expect, leaving a clear 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%, and the schema already explains each parameter (teil_tage, einbau_tage, ersatz_bereit_tage, wechsel_belegt) in detail. The description adds no additional meaning or format guidance beyond what is in the schema, 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 verb (Vergleichen/Compare) and the exact comparison: whether an old device with a confirmed spare part would be usable sooner than the already-verified replacement, factoring in lead time and setup time. It is clear but does not differentiate itself from any sibling tool by name or explicit boundary.

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 use case is implied: deciding between waiting for a spare part versus using a replacement device. However, the description gives no explicit 'use when' / 'do not use when' rules and names no alternative tool, leaving the agent to infer the 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