Skip to main content
Glama

getecoback-raumklima

ersatzteil_kaufpause_reparatur_nutzwerthorizont

Read-only

Ermitteln, ob die zugesagte Wartezeit das selbst gesetzte Zeitfenster für eine noch nutzbare Reparatur aufbraucht — Compare repair wait with a documented end-of-use date rather than assuming the device remains wanted.

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": {
      "ab_heute_bedarf_tage": "<ab_heute_bedarf_tage>",
      "einsetzbar_frueh_tage": "<einsetzbar_frueh_tage>",
      "einsetzbar_spaet_tage": "<einsetzbar_spaet_tage>",
      "zeitangaben_belegt": "<zeitangaben_belegt>"
    },
    "name": "ersatzteil_kaufpause_reparatur_nutzwerthorizont"
  }
}

Input Schema

NameRequiredDescriptionDefault
zeitangaben_belegtYesSind Laufzeit der Haushaltsaufgabe, Teilebezug und Werkstatttermin in diesem Zeitkorridor geklärt?
ab_heute_bedarf_tageYesTage ab heute, bis dieser konkrete Haushalt das Gerät voraussichtlich ohnehin nicht mehr nutzt.
einsetzbar_frueh_tageYesBelegter frühester bestätigter Tag bis Einsatzbereitschaft, in Tagen ab heute.
einsetzbar_spaet_tageYesSpätester bereits begründeter Tag bis Einsatzbereitschaft, ab heute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and locality are covered. The description adds that the comparison must rest on documented inputs rather than assumptions, which is a meaningful behavioral constraint, but it never says what the tool returns (a verdict, a threshold, a boolean) or how 'aufgebraucht' is decided, leaving a real gap for a judgment tool with no output schema.

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 tight clauses with the decision question front-loaded and the methodological caveat second. The English half largely restates the German half, which is for disambiguation and not wasted, but it is not strictly necessary.

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 parameters are well documented in the schema and the read-only nature is covered by annotations, so the core calling information is present. However, with no output schema, the description should explain what the determination yields and how a borderline or unproven case (zeitangaben_belegt=false) is treated; that is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with per-parameter descriptions, so the baseline would be 3. The description still adds semantic framing by identifying ab_heute_bedarf_tage as the documented end-of-use date and contrasting it with assuming the device remains wanted, which clarifies the intent of the comparison rather than restating field text.

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 gives a specific verb-plus-condition ('Ermitteln, ob die zugesagte Wartezeit das selbst gesetzte Zeitfenster ... aufbraucht') and states the comparison being made, so the operation is identifiable. It does not name or differentiate against any sibling tool, so an agent cannot tell from the text alone whether a related ersatzteil_* tool covers part of this question.

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 framing 'Compare repair wait with a documented end-of-use date rather than assuming the device remains wanted' implies the situation in which the tool applies, but gives no explicit when-to-use, when-not-to-use, or alternatives. The agent must infer from context which repair/purchase decisions this gate belongs to.

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