Skip to main content
Glama

getecoback-raumklima

altgeraete_annahmeort_umzug_zwei_belegorte

Read-only

Bei einer Bestellung mit zwei Wohnorten prüfen, welcher ausdrücklich beauftragte Ort für das Altgerät gilt — Compare documented pickup and replacement delivery places without collecting addresses.

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": {
      "abgabeort_neu": "<abgabeort_neu>",
      "mitnahme_ort": "<mitnahme_ort>",
      "tatsaechlicher_altort": "<tatsaechlicher_altort>",
      "belege_gleicher_vorgang": "<belege_gleicher_vorgang>"
    },
    "name": "altgeraete_annahmeort_umzug_zwei_belegorte"
  }
}

Input Schema

NameRequiredDescriptionDefault
mitnahme_ortYesIm Auftrag ausdrücklich angegebener Altgeräteort.
abgabeort_neuYesIm Auftrag bestätigter neuer Abgabeort.
tatsaechlicher_altortYesTatsächlicher Standort des Altgeräts für den Vorgang.
belege_gleicher_vorgangYesSind beides Angaben derselben Bestellung mit eindeutig zugeordnetem 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 a useful constraint in 'without collecting addresses', telling the agent no address data is gathered. It says nothing about how conflicting or 'offen' values are resolved, nor what the comparison yields, which matters for a decision tool.

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?

A single front-loaded sentence states the situation before the operation. The trailing English gloss largely repeats the German clause, which is mild redundancy but not harmful.

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 no explanation of what the comparison returns or how ties are broken, the definition leaves a real gap. It covers when to call it but not enough about the result an agent should expect.

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% and all four parameters, including the three enums, are documented in the schema itself. The description adds no meaning beyond those field descriptions, so the 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 specific verb and resource: check which expressly commissioned place applies to the old appliance for a booking with two residences. It is more than a restatement of the name and the scope clause ('without collecting addresses') narrows it further. It does not explicitly distinguish itself from the many sibling altgeraete_* tools, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trigger condition is stated clearly: use it 'Bei einer Bestellung mit zwei Wohnorten'. That gives an agent a concrete situation in which to select this tool. There is no when-not guidance and no named alternative, which keeps it out of 5 territory.

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