Skip to main content
Glama

getecoback-climate-weather

led_ersatzfassung_schnittstelle_geraetehuelle

Read-only

Sockel, dokumentierte Versorgung und äußere Lampenmaße eines LED-Ersatzes gemeinsam prüfen — Screen a household replacement against the existing fixture specifications.

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": {
      "sockel": "<sockel>",
      "versorgung": "<versorgung>",
      "lampe_laenge_mm": "<lampe_laenge_mm>",
      "lampe_durchmesser_mm": "<lampe_durchmesser_mm>",
      "fassung_laenge_max_mm": "<fassung_laenge_max_mm>",
      "fassung_durchmesser_max_mm": "<fassung_durchmesser_max_mm>",
      "achsen_bestaetigt": "<achsen_bestaetigt>"
    },
    "name": "led_ersatzfassung_schnittstelle_geraetehuelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
sockelYesStimmen die ausdrücklich dokumentierten Sockelkennungen überein?
versorgungYesStimmen die angegebenen Versorgungsdaten laut den Modellunterlagen überein?
lampe_laenge_mmYesGesamtlänge der Lampe an der dokumentierten Bezugsfläche.
achsen_bestaetigtYesSind Referenzkanten, Gehäuseform und gerätespezifisches Datenblatt für dieselbe Kombination geklärt?
lampe_durchmesser_mmYesGrößter angegebener Lampendurchmesser.
fassung_laenge_max_mmYesDokumentierte maximal verfügbare Länge in derselben Bezugslage.
fassung_durchmesser_max_mmYesDokumentierter größter vorgesehener Lampendurchmesser.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that the description says nothing about what the composite check returns — a verdict, a summary, or an echo of the submitted judgments — and gives no hint that the agent itself must supply the ja/nein/offen assessments and the boolean confirmation. That is a real gap for a tool with no output schema.

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 plus a short English restatement — efficient, with the resource list before the usage clause. The German/English duplication is mildly redundant but aids comprehension of a cryptic tool name.

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?

With 7 required parameters fully described in the schema and read-only behavior covered by annotations, the remaining need is an explanation of the verdict, which is absent. For a screening tool the definition is close to complete but leaves the outcome semantics implicit.

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 each of the 7 parameters is already documented in the schema. The description only echoes three of them (Sockel, Versorgung, Lampenmaße) and adds no interpretation of the enum semantics or how lampe_* versus fassung_* values are compared. Baseline 3 applies.

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 specific composite check — socket, documented supply data, and outer lamp dimensions of an LED replacement screened against existing fixture specs. That is a clear verb+resource. It does not, however, distinguish this from similarly named siblings such as led_ersatz_geschlossenes_gehaeuse_umgebung_beleg, so an agent must guess at the boundary.

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?

'Screen a household replacement against the existing fixture specifications' implies the context of use: checking whether a retail LED lamp physically fits a documented fixture. No exclusions, prerequisites, or alternative tools are named, so the when-to-use signal is implied rather than explicit.

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