Skip to main content
Glama

getecoback-raumklima

ledvance_par16_ac45730_merten_meg5137_dimmertest

Read-only

Für eine LEDVANCE-PAR16-Kombination die veröffentlichte Dimmertestzeile nur bei exakt passender Lampenzahl lesen — Retrieve the historical AC45730 × MEG5137-0000 result for one or four lamps only.

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": {
      "lampe": "<lampe>",
      "dimmer": "<dimmer>",
      "stueck": "<stueck>",
      "identischer_testbezug": "<identischer_testbezug>"
    },
    "name": "ledvance_par16_ac45730_merten_meg5137_dimmertest"
  }
}

Input Schema

NameRequiredDescriptionDefault
lampeYesBestätigte Kennung auf dem exakten LEDVANCE-Label.
dimmerYesBestätigte vollständige Merten-Kennung aus vorhandenen Unterlagen.
stueckYesZahl der identischen Lampen im vorliegenden dokumentierten Fall.
identischer_testbezugYesSind Lampenmodell, Dimmernummer und die angegebenen Bedingungen anhand der vorhandenen Unterlagen abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint and openWorldHint=false already establish that this is a safe, closed-world read, so the description's main addition is the strict eligibility condition (exact lamp count, historical record only). It does not say what happens when the count is not 1 or 4 (error, empty result, or refusal) or whether 'identischer_testbezug' must be true to get a row — gaps that matter for a lookup gate.

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

Conciseness3/5

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

The definition is short and front-loads the condition, but it says the same thing twice in German and English, so roughly half the text is duplication. No sentence is wasted in the sense of being irrelevant, but the bilingual restatement reduces information density.

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?

For a read-only four-parameter lookup with a fully documented schema and annotations, the description covers identity and scope adequately. It omits, however, what a caller should do when the lamp count does not match (1 or 4) and whether a 'true' identischer_testbezug is a precondition for a result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the schema: the 'stueck' parameter is declared 1–100 in the schema, yet the description narrows usable values to one or four lamps. That constraint is not derivable from the structured fields alone.

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 verb ('lesen' / 'Retrieve') plus the specific resource — the historical AC45730 × MEG5137-0000 dimmer-test result — and scopes it to one or four lamps. It is clearly distinguishable from generic siblings like ledvance_par16_4099854059810_zwei_modellkennungen, though it never explicitly says how it differs from that related lamp/dimmer lookup.

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 states the triggering condition ('bei exakt passender Lampenzahl', 'for one or four lamps only') and thereby implies exclusion for other lamp counts. It does not name an alternative tool to use when the count differs, so guidance is clear but not fully routable.

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