Skip to main content
Glama

getecoback-raumklima

gefrierschrank_beleuchtung_beleg_entnahmezugang

Read-only

Kläre, ob die im EU-Datenblatt ausgewiesene Lichtquelle eine benötigte Sichtprüfung tatsächlich unterstützt — Scope declared freezer lighting to the observed drawer access task

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": {
      "genaues_modell": "<genaues_modell>",
      "sichtprobe": "<sichtprobe>",
      "probebeleuchtung_passend": "<probebeleuchtung_passend>"
    },
    "name": "gefrierschrank_beleuchtung_beleg_entnahmezugang"
  }
}

Input Schema

NameRequiredDescriptionDefault
sichtprobeYesBeleg im eigenen Ablauf, dass Beschriftung in der unteren Schublade bei geöffneter Tür lesbar war
genaues_modellYesGenaue deutsche Modellkennung
probebeleuchtung_passendYesGleiche Raumbeleuchtung und gleiche Schubladenposition wie im geplanten Einsatz

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare a read-only, closed-world check, so the safety profile is covered. The description does add a genuine behavioral trait — it narrows the declared datasheet lighting claim to the observed drawer-access task — but says nothing about how the three required inputs are combined, what a record looks like, or how an "offen" outcome is treated.

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?

It is a single short, front-loaded statement, which is appropriately sized. The English half largely restates the German half, which is mild redundancy rather than a structural flaw.

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 a fully documented three-parameter schema and no output schema, the main remaining need is what the tool returns or records and how the evidence states are interpreted. The description implies a judgment outcome but does not specify it, leaving it minimally adequate rather than complete.

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 two documented enums, so the schema already carries the parameter meaning. The description's mention of the datasheet light source and the visual-inspection/drawer-access context loosely maps to sichtprobe and probebeleuchtung_passend, but adds no format or value semantics beyond the schema — baseline 3.

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 description frames a specific question (whether the light source declared in the EU datasheet supports a required visual inspection) and adds a scoping phrase about freezer lighting vs. the observed drawer-access task. However, the verb is abstract ("Kläre, ob ...") and it never states what the tool actually produces or does with the inputs, so an agent cannot fully tell it apart from near-neighbours like gefrierschrank_tuerwinkel_schublade_entnahme_pruefung.

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 explicit when-to-use or when-not-to-use guidance and no named alternative among the many narrow freezer-evidence siblings. The scope clause hints at the applicable situation but leaves the routing decision to inference.

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