Skip to main content
Glama

getecoback-climate-weather

duschhalter_gebraucht_auflage_und_etikett_beleg

Read-only

Bei einem gebrauchten Halter Artikelbeleg und tatsächlich fotografiertes Kontaktteil unabhängig prüfen — Distinguish missing model evidence from a visibly different attachment.

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": {
      "etikett_geprueft": "<etikett_geprueft>",
      "kontaktteil_vollstaendig_abgebildet": "<kontaktteil_vollstaendig_abgebildet>",
      "kontaktteil_identitaet": "<kontaktteil_identitaet>",
      "modellfoto_ist_das_stueck": "<modellfoto_ist_das_stueck>"
    },
    "name": "duschhalter_gebraucht_auflage_und_etikett_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
etikett_geprueftYesOriginalartikelnummer ist vollständig belegt.
kontaktteil_identitaetYesDas vorhandene Kontaktteil lässt sich der ursprünglichen Unterlage zuordnen.
modellfoto_ist_das_stueckYesAbbildung ist nachweislich dieses Einzelstück statt ein Hersteller-Bild.
kontaktteil_vollstaendig_abgebildetYesDie sichtbare Auflage des konkret angebotenen Halters ist vollständig erkennbar.

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 that the two checks must be made independently and that missing evidence must not be conflated with contradictory evidence — genuinely useful behavioural framing. It does not explain, however, what happens to the four supplied judgements (recorded, validated, returned) or what the caller receives, which is significant for a tool whose inputs are all required assertions.

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?

Very short and front-loaded with the object and the two evidence sources; nothing is padding. The German sentence followed by an English restatement of the same idea is mildly redundant, and the em-dash construction is compact to the point of being cryptic, but the size is appropriate for the tool's narrow scope.

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 annotation detail about results, the description carries the burden of explaining what the caller gets back and how the four judgements combine — which it does not. It is complete about *what* is being assessed but incomplete about outcome and result interpretation.

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%, so the four parameters and the 'bestaetigt/abweichend/offen' enum are already fully self-documenting; baseline 3 applies. The description adds only a conceptual mapping (Artikelbeleg → label check, fotografiertes Kontaktteil → contact-part checks) and the requirement that they be assessed independently, without clarifying the distinction between 'offen' and 'abweichend' beyond the one-line purpose.

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 subject (gebrauchter Duschhalter), two distinct evidence sources (Artikelbeleg and tatsächlich fotografiertes Kontaktteil) and a specific verb (unabhängig prüfen), plus the failure modes it discriminates. An agent can tell it is an evidence-verification tool rather than a plain lookup or a drawing/measurement tool. It stops short of stating what the tool operationally produces (a verdict, a stored judgement), and it does not differentiate itself from the numerous other '*_beleg' siblings by name.

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 clause 'Distinguish missing model evidence from a visibly different attachment' implies the situation in which this tool applies, so usage is inferable. However, there is no explicit when-to-use, no when-not, and no named alternative among the many related shower-holder evidence tools (e.g. kontaktumfang_skizze, fugenfeld_kontaktschablone). Guidance is implied 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