Skip to main content
Glama

getecoback-climate-weather

altgeraete_marktplatz_verkaeufer_logistikkette

Read-only

Marktplatz, vertraglichen Vertreiber und ausführenden Abholdienst in den konkreten Belegen auseinanderhalten — Trace a pickup commitment to the seller or its verified carrier.

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": {
      "vertragspartner_bestaetigt": "<vertragspartner_bestaetigt>",
      "zusage_von": "<zusage_von>",
      "logistik_beauftragung_belegt": "<logistik_beauftragung_belegt>",
      "zusage_exakt_fuer_bestellung": "<zusage_exakt_fuer_bestellung>"
    },
    "name": "altgeraete_marktplatz_verkaeufer_logistikkette"
  }
}

Input Schema

NameRequiredDescriptionDefault
zusage_vonYesWer bestätigte die konkrete Altgeräteabholung?
vertragspartner_bestaetigtYesDer tatsächliche Verkäufer ist aus der konkreten Bestellunterlage eindeutig bestimmbar?
logistik_beauftragung_belegtYesIst bei Logistikzusage die Beauftragung durch denselben Verkäufer für diese Bestellung belegt?
zusage_exakt_fuer_bestellungYesBezieht sich die Zusage ausdrücklich auf dieselbe Bestellung und die Altgerätemitnahme?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the description is not obligated to restate it — it correctly does not. What it omits is the behavior that matters here: whether this is a pure rule-based evaluation of supplied booleans, what it returns, and what happens when the evidence is ambiguous (the enum value "offen" implies an indeterminate outcome, but the description never says so).

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?

It is short, but the content is a German sentence immediately restated in English without adding new information, so roughly half the text is duplication. Front-loading is fine, yet the single useful clause (trace commitment to seller or carrier) is buried behind the German enumeration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is the only place an agent could learn what result to expect from these four evidence booleans, and it says nothing about the returned assessment or how conflicting inputs are resolved. For a classification/attribution tool with four required inputs and an "offen" branch, that is a real completeness gap.

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 required fields carries a German description, including the four-value enum for zusage_von, so the schema does the heavy lifting. The description's phrase "in den konkreten Belegen" does add framing by signalling that all inputs must be grounded in the concrete order documents, which goes slightly beyond the schema.

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 English half ("Trace a pickup commitment to the seller or its verified carrier") names a concrete object and a discrimination task, and the German half adds the three parties to be separated (marketplace, contractual distributor, executing pickup service). But it never states what the tool actually produces — a verdict, a classification label, a boolean outcome — so the agent knows the domain yet not the deliverable, and no sibling is named for contrast.

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?

There is no when-to-use guidance, no when-not-to-use, and no pointer to any of the many altgeraete_* siblings that deal with adjacent evidence questions. The agent must infer from the parameter names alone that this is the tool for resolving the seller-vs-carrier attribution question, which is thin routing guidance in a dense sibling cluster.

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