Skip to main content
Glama

getecoback-climate-weather

altgeraete_abholvorgang_tatsaechliche_uebergabe

Read-only

Eine für dieselbe Bestellung protokollierte Altgeräteabholung von Neu-Zustellung, erfolglosem Versuch und Terminankündigung unterscheiden — Reconcile actual handover separately from delivery of the replacement.

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": {
      "neu_abgegeben": "<neu_abgegeben>",
      "abholstatus": "<abholstatus>",
      "altgeraet_eindeutig": "<altgeraet_eindeutig>"
    },
    "name": "altgeraete_abholvorgang_tatsaechliche_uebergabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
abholstatusYesWas belegt das tatsächliche Ergebnis der Altgerätemitnahme?
neu_abgegebenYesWurde die Neulieferung bestätigt abgeschlossen?
altgeraet_eindeutigYesBezieht sich der aufgezeichnete Status eindeutig auf das vereinbarte Altgerät und nicht auf eine andere Sendung?

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?

The readOnlyHint=true annotation already establishes that this is a safe read operation, and openWorldHint=false indicates a closed-world context. The description adds useful semantic context that the reconciliation is specifically about actual handover versus delivery, but it does not describe the result or how the classification is produced.

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 compact and front-loads the scenario before stating the reconciliation goal. The German/English duplication is somewhat redundant, but the text remains efficient and easy to scan.

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 three-parameter, fully described read-only classification tool, the definition covers the semantic distinction it is meant to make. However, with no output schema, it does not explain what the tool returns or how the reconciliation result should be interpreted, leaving a notable gap for an agent invoking it.

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 three parameters are already documented in the schema, including the abholstatus enum values. The description mentions the relevant distinctions but adds no parameter-level meaning, formats, or interaction rules beyond what the schema provides, making the baseline 3 appropriate.

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 names the resource (Altgeräteabholung) and the operation of distinguishing/reconciling actual handover from replacement delivery, failed attempts, and appointment announcements. It is clear enough to identify the tool's domain, but it does not explicitly state the output or differentiate it from the many similar Altgeräte sibling tools.

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 description implies when the tool is relevant: when an actual old-device handover must be separated from a new delivery, a failed attempt, or an appointment-only record. It does not give explicit when-to-use/when-not-to-use guidance or route the agent to alternatives among the many similarly named sibling tools.

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