Skip to main content
Glama

getecoback-raumklima

altgeraete_mitnahmewunsch_zur_zustelltour

Read-only

Von einer gesendeten Rückgabeabsicht bis zur ausdrücklichen Übernahme in den Zustellauftrag sichtbare Belegstufen unterscheiden — Track an old-appliance request through checkout confirmation to the carrier work order.

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": {
      "wunsch_gesendet": "<wunsch_gesendet>",
      "in_kaufbestaetigung": "<in_kaufbestaetigung>",
      "im_zustellauftrag": "<im_zustellauftrag>",
      "varianten_zuordnung_geprueft": "<varianten_zuordnung_geprueft>"
    },
    "name": "altgeraete_mitnahmewunsch_zur_zustelltour"
  }
}

Input Schema

NameRequiredDescriptionDefault
wunsch_gesendetYesDie Abholabsicht wurde nachweislich übermittelt?
im_zustellauftragYesDer Zustellauftrag nennt ausdrücklich dieselbe Mitnahme?
in_kaufbestaetigungYesDie Kaufbestätigung nennt ausdrücklich die Mitnahme desselben Altgeräts?
varianten_zuordnung_geprueftYesBelege, Händler und Altgerät gehören eindeutig zu derselben Bestellung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that the description adds nothing behavioral: it does not say whether the tool only inspects the supplied flags, whether it returns a gap diagnosis, or what a true/false outcome implies for the delivery tour.

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

Conciseness3/5

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

One sentence, but it is given twice in German and English without the English adding precision, and the dash-joined structure mixes the workflow framing with the tool's action. Front-loading the actual operation would help.

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

Completeness2/5

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

For a read-only checker with four required flags and no output schema, the description should explain what the result represents and how the stages relate. Neither is present, so an agent knows the vocabulary but not the outcome or its meaning.

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 booleans documented in German, so the schema carries the semantics. The description mentions the concept of evidence stages but adds no interpretation of the individual flags or of their interactions (e.g. what combination is invalid).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

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

The description restates the tool name in prose ('Vom Mitnahmewunsch ... bis zur Zustelltour') and adds the notion of distinguishing 'sichtbare Belegstufen', but it never states the actual operation — does it validate the four flags, list missing stages, or compare documents? An agent cannot tell what calling it accomplishes beyond the title.

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?

No guidance on when to use this instead of the many sibling altgeraete_* tools (e.g. abholhinweis_vertragsmoment_beleg, annahme_und_weiterverwendung_beleg). No prerequisites and no exclusions are given, so selection among near-identical siblings is left to guesswork.

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