Skip to main content
Glama

getecoback-raumklima

led_eprel_qr_modellbeleg_verpackung

Read-only

Einen gelesenen QR-Verweis mit der Modellkennung auf der Verpackung abgleichen — Check the EPREL destination and model identity, not the mere presence of a QR code.

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": {
      "qr_ziel": "<qr_ziel>",
      "marke": "<marke>",
      "modell": "<modell>",
      "datenblatt_zur_packung": "<datenblatt_zur_packung>"
    },
    "name": "led_eprel_qr_modellbeleg_verpackung"
  }
}

Input Schema

NameRequiredDescriptionDefault
markeYesStimmt der Anbieter im gelesenen Datensatz mit dem Label überein?
modellYesStimmt die vollständige Modellkennung einschließlich Zusätzen überein?
qr_zielYesVorliegendes Ziel des gedruckten Codes.
datenblatt_zur_packungYesWurde die Zuordnung für diese konkrete Verpackung und denselben Markt belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish a read-only, closed-world operation. The description adds that the tool evaluates an already-read reference rather than merely detecting a QR code, but it does not explain how unresolved or conflicting evidence affects the outcome or what result is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The wording is compact and front-loads the reconciliation task, followed immediately by the key EPREL and model-identity caveat. The English portion adds substantive scope and the QR-presence exclusion rather than merely repeating the German text.

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

Completeness4/5

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

For a focused four-input evidence check, the description, fully documented schema, and read-only annotations provide nearly enough information to select and invoke the tool correctly. The main gap is the lack of an output schema or description of the returned assessment and how the four inputs contribute to it.

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 schema already documents all four required inputs and their allowed values. The description reinforces the meaning of qr_ziel and modell, but adds no further semantics for marke or datenblatt_zur_packung and no rules for combining the assessments.

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 specifies a concrete operation: reconciling an already-read QR reference with the model identifier on the packaging, including the EPREL destination and model identity. It clearly distinguishes this from a superficial QR-presence check, but does not explicitly contrast itself with any sibling tool.

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?

It gives a clear use case—substantive verification of the QR destination and model identity—and explicitly warns that the mere presence of a QR code is insufficient. It does not provide an alternative or escalation path for unresolved codes, incorrect destinations, or mismatched models.

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