Skip to main content
Glama

getecoback-climate-weather

altgeraete_abholversuch_grund_und_erneute_zusage

Read-only

Nach einem erfolglosen Mitnahmeversuch einen schriftlichen Hinderungsgrund von einem belegten Folgetermin unterscheiden — Triage an unsuccessful pickup using the documented obstacle and latest reassignment.

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": {
      "ergebnis": "<ergebnis>",
      "grund": "<grund>",
      "folgetermin_bestaetigt": "<folgetermin_bestaetigt>",
      "grund_aufgeloest": "<grund_aufgeloest>"
    },
    "name": "altgeraete_abholversuch_grund_und_erneute_zusage"
  }
}

Input Schema

NameRequiredDescriptionDefault
grundYesVom zuständigen Dienst dokumentierter Hinderungsgrund.
ergebnisYesBestätigtes Ergebnis des ersten Termins.
grund_aufgeloestYesDer Anbieter hat den dokumentierten Hinderungsgrund ausdrücklich als geklärt bestätigt?
folgetermin_bestaetigtYesEin neuer Termin für dasselbe Altgerät wurde ausdrücklich bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 and the bar is lower. The description adds that this is a triage/assessment step after a failed pickup, which is real context, but it says nothing about how ambiguous or contradictory inputs (e.g. grund='offen' with grund_aufgeloest=true) are handled or what the assessment produces.

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, so length is fine, but it is bilingual in a way that duplicates content rather than layering information — the English half is a paraphrase, not an addition. The key qualifying condition (post-failed-pickup) is front-loaded, which helps.

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?

With four required parameters, no output schema, and a classification-style operation, the description should convey what the triage concludes or how the four inputs combine. It conveys the scenario but not the decision logic or outcome, leaving a meaningful gap for an agent that must interpret the result.

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 enum value documentation on two parameters, so the schema does the heavy lifting and a baseline 3 applies. The description does loosely map its wording ('schriftlicher Hinderungsgrund' → grund, 'belegter Folgetermin' → folgetermin_bestaetigt), but it adds no interpretation rules linking those fields to the triage decision.

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

Purpose3/5

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

The description names a specific subject (an unsuccessful pickup attempt, a documented obstacle, a confirmed follow-up appointment) and a specific operation ('distinguish', 'Triage'). But the German clause and the English clause restate the same idea rather than sharpening it, and the agent is left unsure whether the tool returns a classification or performs a state change. It is differentiated from pickup-related siblings only indirectly.

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 phrase 'Nach einem erfolglosen Mitnahmeversuch' implies a triggering context, but there is no explicit when-to-use or when-not-to-use statement and no alternative tool named. None of the many siblings (e.g. altgeraete_abholvorgang_tatsaechliche_uebergabe, altgeraete_termin_neulieferung_verschoben_mitnahme) are referenced, so routing must be inferred from names 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