Skip to main content
Glama

getecoback-climate-weather

altgeraete_wechsel_nutzungsluecke_tatsaechlich

Read-only

Nach der tatsächlichen Übergabe des Altgeräts die beobachtete Lücke bis zur ersten bestätigten Neunutzung nachvollziehen — Compute an observed service gap using the first usable replacement date rather than a delivery promise.

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": {
      "alt_letzte_nutzung": "<alt_letzte_nutzung>",
      "alt_abgegeben": "<alt_abgegeben>",
      "neu_geliefert": "<neu_geliefert>",
      "neu_erstmals_nutzbar": "<neu_erstmals_nutzbar>"
    },
    "name": "altgeraete_wechsel_nutzungsluecke_tatsaechlich"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_abgegebenYesTatsächlich bestätigter Tag der Übergabe des Altgeräts. YYYY-MM-DD, leer wenn nicht belegt.
neu_geliefertYesTag der dokumentiert erfolgten Neulieferung. YYYY-MM-DD, leer wenn nicht belegt.
alt_letzte_nutzungYesLetzter Tag belegter Nutzung des Altgeräts. YYYY-MM-DD, leer wenn nicht belegt.
neu_erstmals_nutzbarYesErster Tag der bestätigten Nutzbarkeit des neuen Geräts für dieselbe Aufgabe. YYYY-MM-DD, leer wenn nicht belegt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral content beyond that: the gap is measured from first confirmed usability rather than a delivery promise, which is precisely the semantic decision an agent must understand before trusting the result. It says nothing about what is returned when dates are blank, though the schema hints at this.

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 scope condition is front-loaded and the contrast with the delivery-promise variant follows immediately, so the two sentences earn their place. The German/English duplication of the same idea is mild redundancy but aids clarity for a bilingual tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-date, side-effect-free calculation with full schema coverage and no output schema, the description supplies the essential conceptual model. The only shortfall is that it never states what the computed result looks like (e.g. a day count between the two confirmed dates), which matters slightly more because no output schema exists.

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 each of the four dates documented individually including YYYY-MM-DD format and empty-when-unproven semantics. The description only echoes the concepts of handover and first usability, adding no format, ordering, or validation detail beyond 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific computation (the observed service gap after actual handover of the old device) and contrasts it with the alternative basis it rejects — a mere delivery promise. An agent can distinguish this from the many sibling 'Wechsel' tools that track logistics or contracts rather than computing a usage gap.

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?

It states the triggering condition clearly: use this after the actual handover ('Nach der tatsächlichen Übergabe des Altgeräts'), and it implies the observation window ends at the first confirmed re-use. It stops short of naming explicit exclusions or a named sibling tool to use instead when only promised dates exist.

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