Skip to main content
Glama

getecoback-raumklima

geraet_nach_reparatur_eigenes_ersatzgeraet_abbauen

Read-only

Vor Abgabe eines übergangsweise bereitgehaltenen Zweitgeräts aufeinanderfolgende Nutzungstage prüfen — Review a documented trial before releasing a temporary backup.

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": {
      "regelbetrieb_belegt": "<regelbetrieb_belegt>",
      "plan_tage": "<plan_tage>",
      "belegt_tage": "<belegt_tage>",
      "stoerung_beobachtet": "<stoerung_beobachtet>",
      "reserve_tage": "<reserve_tage>"
    },
    "name": "geraet_nach_reparatur_eigenes_ersatzgeraet_abbauen"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_tageYesSelbst geplante Mindestzahl zusammenhängend beobachteter Nutzungstage.
belegt_tageYesAnzahl tatsächlich aufeinanderfolgender beobachteter Nutzungstage.
reserve_tageYesTage, die das Zweitgerät ab heute weiter bereitgehalten werden kann.
regelbetrieb_belegtYesIst das reparierte Gerät nach dokumentierter Rückmeldung für genau diese Routine einsatzbereit?
stoerung_beobachtetYesTrat währenddessen eine relevante Störung oder eine vom Service ausgeschlossene Nutzung auf?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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, and 'prüfen'/'Review' is consistent with that safety profile. Beyond the annotations the description contributes only the decision context (a documented trial before release) and nothing about how the check concludes, what is returned, or what a negative outcome implies — notable given there is 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?

A single front-loaded sentence with the trigger condition stated first, then the action. It is efficient overall, though the German/English duplication restates the same content rather than adding information.

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 decision tool with five required numeric/boolean inputs and no output schema, the description explains when to run it but not what result to expect or how to act on it. The schema covers the inputs fully, so the remaining gap is outcome semantics rather than parameter coverage.

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%, so all five required parameters carry their own meanings and the baseline is 3. The description's only added semantic is the notion of consecutive day counts, which loosely maps to plan_tage/belegt_tage but adds no format or interpretation detail beyond the schema.

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 ('prüfen'/'Review') and object ('aufeinanderfolgende Nutzungstage' for a 'übergangsweise bereitgehaltenes Zweitgerät'), and usefully reframes the name's 'abbauen' as an assessment step rather than an actual teardown. It does not, however, distinguish this check from nearby sibling evaluations such as the temporary-coverage or loan-window tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Vor Abgabe eines übergangsweise bereitgehaltenen Zweitgeräts' states a clear triggering moment for calling the tool. There is no explicit when-not guidance and no alternative tool is named, so the agent must infer routing from the sibling list alone.

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