Skip to main content
Glama

getecoback-climate-weather

geraet_service_leihzeit_anschlussfenster

Read-only

Eine Rückgabefrist für ein vorhandenes Ersatzgerät mit dem bestätigten Übergabefenster abgleichen — Identify a potential service-loaner coverage gap.

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": {
      "rueckgabe_tag": "<rueckgabe_tag>",
      "uebergabe_frueh_tag": "<uebergabe_frueh_tag>",
      "uebergabe_spaet_tag": "<uebergabe_spaet_tag>",
      "fenster_bestaetigt": "<fenster_bestaetigt>"
    },
    "name": "geraet_service_leihzeit_anschlussfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
rueckgabe_tagYesLetzter verfügbarer Tag des Leihgeräts als Tag ab heute.
fenster_bestaetigtYesDas Übergabefenster ist vom Service ausdrücklich bestätigt?
uebergabe_frueh_tagYesFrühester dokumentierter Tag der Geräteübergabe im selben Raster.
uebergabe_spaet_tagYesSpätester dokumentierter Übergabetag oder eigene obere Planungsgrenze.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare this as a read-only, closed-world operation, which matches the analytical 'abgleichen' wording. The description adds that the goal is identifying a potential service-loaner coverage gap, but it does not explain how the gap is determined or what the result represents.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no filler. The bilingual gloss is compact and directly supports the core purpose without distracting from it.

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 four-parameter comparison tool with rich schema descriptions and read-only annotations, the definition covers the core action adequately. However, because there is no output schema, it leaves the nature of the returned coverage-gap result unspecified.

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 four parameters are already documented in detail, including the day offsets and the confirmation boolean. The description references the return deadline and confirmed handover window but adds no syntax or interpretation 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 states a specific action: comparing the return deadline of an existing loaner device with the confirmed handover window to identify a potential coverage gap. The verb 'abgleichen' and the two resources are clear, though no sibling tool is named to sharpen differentiation.

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?

The description implies the tool is used for coverage-gap analysis, but it gives no explicit when-to-use guidance, prerequisites, or alternatives among the many device-service siblings. An agent must infer the appropriate situation from the purpose 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