Skip to main content
Glama

getecoback-climate-weather

ersatzteil_verpackung_beleg_widerspruch_inhalt

Read-only

Bestellbestätigung, äußeres Etikett und vom Anbieter bestätigten Inhalt auf Abweichungen abgleichen — Hold a package identity mismatch instead of accepting an outer label as proof.

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": {
      "bestaetigung_richtig": "<bestaetigung_richtig>",
      "etikett": "<etikett>",
      "inhalt": "<inhalt>"
    },
    "name": "ersatzteil_verpackung_beleg_widerspruch_inhalt"
  }
}

Input Schema

NameRequiredDescriptionDefault
inhaltYesIst die exakte Nummer der tatsächlichen Ware unabhängig durch die zuständige Stelle bestätigt?
etikettYesLaut vorhandener Fotodokumentation nennt das äußere Etikett dieselbe Variante?
bestaetigung_richtigYesNennt die Bestellbestätigung die bestätigte benötigte Teilenummer und Variante?

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 real value by stating the decision policy (a mismatch is held rather than resolved by the outer label), but the word 'Hold' sits uneasily with a read-only tool and the description never clarifies the resulting verdict or whether any record is persisted.

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 tight sentences, with the comparison scope front-loaded and the policy statement second. Dense but every clause contributes; the only minor cost is the bilingual phrasing that repeats the same idea twice.

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 three required parameters are documented and the tool is a simple read-only comparison, so little is missing on the input side. However, with no output schema, the description should state what the comparison returns (a mismatch verdict, a hold flag, a reason) and it does not.

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 both enum parameters carry explicit questions, so the schema does the heavy lifting. The description only maps its three evidence sources (Bestellbestätigung, Etikett, Inhalt) onto the parameters without adding format, precedence, or edge-case semantics.

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 (comparing order confirmation, outer label, and provider-confirmed content for deviations) and its outcome (hold an identity mismatch). This is a specific verb+resource, but it never contrasts itself with close siblings such as ersatzteil_marktbeleg_typenschild_kaufserie or ersatzteil_mengenabgleich_einzelpackung_rueckbehalt, so an agent must infer the boundary.

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?

Usage is only implied: the three-way comparison and the phrase 'instead of accepting an outer label as proof' hints that this tool is for cases where label evidence alone is insufficient. There is no explicit when-to-use, when-not-to-use, or named alternative among the many ersatzteil_* siblings.

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