Skip to main content
Glama

getecoback-raumklima

altgeraete_zusteller_vertretung_fuer_alt_und_neu

Read-only

Eine abgestimmte Vertretung bei Lieferung auf die separat bestätigten Rollen für Neuannahme und Altübergabe prüfen — Keep replacement acceptance separate from the confirmed delegation of the old appliance.

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": {
      "person_bestaetigt": "<person_bestaetigt>",
      "neu_annahme_moeglich": "<neu_annahme_moeglich>",
      "alt_uebergabe_moeglich": "<alt_uebergabe_moeglich>",
      "selber_termin": "<selber_termin>"
    },
    "name": "altgeraete_zusteller_vertretung_fuer_alt_und_neu"
  }
}

Input Schema

NameRequiredDescriptionDefault
selber_terminYesGelten die Belege für denselben vereinbarten Termin?
person_bestaetigtYesDie vertretende erwachsene Person hat die konkreten Aufgaben angenommen?
neu_annahme_moeglichYesStatus der Neugeräteannahme durch die Vertretung laut konkretem Anbieterbeleg.
alt_uebergabe_moeglichYesStatus der Altgeräteübergabe durch dieselbe Vertretung.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a real behavioral rule beyond that: the two roles are confirmed independently, so a confirmation for one does not carry the other. It does not disclose what the tool returns or how conflicting statuses (e.g. 'bestaetigt' for Neuannahme but 'offen' for Altübergabe) are resolved, which is the main remaining gap.

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?

Two compact sentences with the action front-loaded and the constraint second; nothing is padded. The bilingual split is not pure duplication — the German names the operation, the English states the separation rule — though the German clause is dense enough that one sentence has to be re-read.

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?

Four required parameters, two of them enums with an 'offen' state, and no output schema; the description never indicates what verdict or classification comes back, which matters for a validation-style tool. The separation rule is the essential missing-context piece and it is supplied, so the definition is workable but not fully self-sufficient.

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 coverage is 100% and each of the four parameters already carries a description plus enums for the two status fields, so the schema does the heavy lifting. The description contributes only indirectly, by motivating why neu_annahme_moeglich and alt_uebergabe_moeglich must be treated as independent confirmations. Baseline 3 is 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 a concrete action (prüfen) on a concrete object: a coordinated substitution (Vertretung) at delivery, evaluated against the separately confirmed roles for Neuannahme and Altübergabe. That is more than a restatement of the name and is distinguishable from the surrounding 'Abholversuch'/'Übergabe' siblings. It stops short of full clarity because the German syntax ('auf die ... Rollen prüfen') leaves it slightly ambiguous whether the tool verifies, decides, or merely classifies the case.

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 English half supplies an implicit operating rule — replacement acceptance must be kept separate from the confirmed delegation of the old appliance — which tells the agent in what situation the check matters. There is no explicit when-to-use/when-not-to-use statement and no alternative tool is named, so the routing guidance remains inferred rather than stated.

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