Skip to main content
Glama

getecoback-raumklima

ledvance_par16_4099854059810_zwei_modellkennungen

Read-only

Die zwei dokumentierten Revisionen derselben deutschen LEDVANCE-PAR16-Faltschachtel anhand der vollständigen Modellkennung trennen — Disambiguate the two variants published for one exact retail GTIN.

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": {
      "gtin": "<gtin>",
      "modell": "<modell>",
      "markt_de": "<markt_de>"
    },
    "name": "ledvance_par16_4099854059810_zwei_modellkennungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gtinYesVollständige bereits belegte GTIN der Faltschachtel.
modellYesVollständige Kennung aus dem exakten Label/Herstellerbeleg. Leerzeichen bei AC-Kennungen weglassen.
markt_deYesIst die deutsche Herstellerseite die passende Quelle?

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 only documented revisions are considered and that the German manufacturer page is the relevant source, which is useful context. It never states what the disambiguation actually yields (a chosen variant, a mapping, a verdict), leaving the core behavior unexplained.

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 with the operation stated first. The German/English duplication conveys the same content twice, which is slight waste but not confusing, and there is no filler preamble.

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?

Three required, fully documented, enum-constrained parameters keep the schema burden low. However, with no output schema, the description should say what a successful disambiguation returns and how 'andere'/'offen' inputs are handled; that gap is material for a tool whose whole purpose is choosing between two variants.

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%, with enum values and per-field descriptions, so the baseline is 3. The description reinforces the 'vollständige Modellkennung' and 'exact retail GTIN' constraints but adds no new syntax or edge-case meaning beyond the schema.

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 states a specific verb and object: separate the two documented revisions of the same German LEDVANCE PAR16 folding box using the complete model identifier. An agent can understand the operation without opening the schema. It does not name or contrast any sibling tool, so it stops short of 5.

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 implied by the framing 'the two variants published for one exact retail GTIN' — call it when a single GTIN resolves to two documented revisions. There is no explicit when-not guidance, no prerequisites, and no mention of the sibling LEDVANCE tool that handles a different question.

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