Skip to main content
Glama

getecoback-climate-weather

altgeraete_termin_neulieferung_verschoben_mitnahme

Read-only

Bei einer verschobenen Lieferung zwischen ausdrücklich mitverschobener und separat am alten Termin bestätigter Altgeräteabholung unterscheiden — Preserve a pickup status when the new-device delivery date changes.

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": {
      "alter_liefertag": "<alter_liefertag>",
      "neuer_liefertag": "<neuer_liefertag>",
      "abholnachtrag": "<abholnachtrag>",
      "gleicher_auftrag": "<gleicher_auftrag>"
    },
    "name": "altgeraete_termin_neulieferung_verschoben_mitnahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
abholnachtragYesWas steht im Änderungsbeleg zur Mitnahme?
alter_liefertagYesUrsprünglich bestätigter Tag der Neulieferung. YYYY-MM-DD, leer wenn nicht belegt.
neuer_liefertagYesSpäter bestätigter neuer Liefertag derselben Bestellung. YYYY-MM-DD, leer wenn nicht belegt.
gleicher_auftragYesGilt der Änderungsbeleg für denselben Verkäufer, dieselbe Bestellung und dasselbe Altgerät?

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, so the safety profile is covered. The description adds only the evaluation intent ('Preserve a pickup status'), saying nothing about what the outcome means or how the preserved/not-preserved state is expressed, which is modest added value over the annotations.

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?

A single front-loaded sentence plus a compact English rendering; nothing is redundant and the condition precedes the action. No filler, no repetition of schema or annotation content.

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 4-required-parameter classification tool with no output schema, the definition supplies the decision axis but not what the tool actually produces or how the two branches differ downstream. Adequate to attempt a call, incomplete for interpreting the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description goes slightly beyond by spelling out the two decisive cases ('ausdrücklich mitverschobene' vs 'separat am alten Termin bestätigt') that map onto the abholnachtrag enum, giving an agent the discrimination axis rather than just the field labels.

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?

Names a concrete decision task ('zwischen ... unterscheiden') scoped to a rescheduled new-device delivery, plus an English gloss ('Preserve a pickup status when the new-device delivery date changes'). The resource and condition are identifiable, though the phrasing is abstract and it does not name any sibling tool it must be told apart from.

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 trigger condition is implied by 'Bei einer verschobenen Lieferung' — i.e. use this when a delivery date changed. There is no explicit when-not, no prerequisite check, and no routing to related tools such as the other Altgeräte pickup tools listed as siblings.

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