Skip to main content
Glama

getecoback-climate-weather

altgeraete_neuannahme_abbruch_mitnahmebindung

Read-only

Bei ausgefallener Neulieferung unterscheiden, ob ein schriftlicher Mitnahmeauftrag ausdrücklich unabhängig bleibt oder nur mit der Neulieferung galt — Check the pickup dependency when the replacement is not handed over.

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": {
      "neue_lieferung": "<neue_lieferung>",
      "mitnahme_bedingung": "<mitnahme_bedingung>",
      "altbereits_uebergeben": "<altbereits_uebergeben>",
      "korrekter_bestellbezug": "<korrekter_bestellbezug>"
    },
    "name": "altgeraete_neuannahme_abbruch_mitnahmebindung"
  }
}

Input Schema

NameRequiredDescriptionDefault
neue_lieferungYesTatsächlicher Stand der Neugeräteübergabe.
mitnahme_bedingungYesAusdrückliche Bindung im konkreten Zustellauftrag.
altbereits_uebergebenYesWurde das Altgerät bereits tatsächlich übergeben?
korrekter_bestellbezugYesDie Vorgänge betreffen exakt das alte und das neue Gerät dieser Bestellung?

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 annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a purely internal, side-effect-free evaluation. The description adds the substantive framing that the check concerns the binding of the pickup order to the replacement delivery. It does not indicate what kind of verdict is produced or how a partially documented case is treated, which matters for a rule-evaluation tool with no output schema.

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 definition is a single compact sentence with the trigger condition front-loaded, plus a short English gloss that restates the same check. The gloss is slightly redundant, but nothing is wasted and the decision to be made is immediately visible.

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?

All four required parameters are documented by the schema and the read-only nature is covered by annotations, so the input side is complete. The gap is on the outcome side: with no output schema, the description should say what the tool returns — for example whether it yields a binding verdict, a flag, or a reasoned classification — and how the 'nicht_dokumentiert' case is resolved.

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%, including enum value descriptions for 'neue_lieferung' and 'mitnahme_bedingung', so the schema already carries the parameter meaning. The description echoes the same concepts ('ausgefallene Neulieferung', 'schriftlicher Mitnahmeauftrag') without adding interpretation rules for the boolean inputs such as 'korrekter_bestellbezug'. Baseline 3 applies.

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 a concrete decision: when the replacement delivery has failed, distinguish whether a written pickup order remains expressly independent or was valid only together with the replacement. The verb ('unterscheiden') and the scenario are specific enough for an agent to recognize the evaluation task. It does not name any sibling tool, so differentiation from the many similar 'altgeraete_*' tools rests on the scenario wording alone.

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 clearly ('Bei ausgefallener Neulieferung'), which gives an agent enough context to know when the tool applies. However, there is no explicit statement of when not to use it and no named alternative for adjacent cases such as a merely postponed delivery or a pickup already performed.

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