Skip to main content
Glama

getecoback-raumklima

led_ersatz_geschlossenes_gehaeuse_umgebung_beleg

Read-only

Eine modellbezogene Angabe zum geschlossenen Leuchtengehäuse von Innenraum- oder Außeneignung trennen — Check the specific enclosure condition instead of generalizing an indoor-use claim.

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": {
      "gehaeuse": "<gehaeuse>",
      "quellenbeleg": "<quellenbeleg>",
      "identische_einsatzbedingungen": "<identische_einsatzbedingungen>"
    },
    "name": "led_ersatz_geschlossenes_gehaeuse_umgebung_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
gehaeuseYesBelegte vom Leuchtenhersteller beschriebene Bauform.
quellenbelegYesAusdrücklich dokumentierte Aussage der konkreten Lichtquelle.
identische_einsatzbedingungenYesGenaue Modelle und die zum Nutzort gehörenden Bedingungen wurden abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the conceptual distinction between a model-specific enclosure statement and a generalized indoor-use claim, which is useful framing, but it says nothing about what is recorded, returned, or how conflicting evidence (e.g. 'unklar') is handled.

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?

It is short, but the German half is malformed and the English half largely restates it, so the two halves do not form a clean front-loaded statement. There is redundancy without added precision.

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 simple read-only, three-parameter evidence/classification tool with no output schema, the description conveys the topic and the guard-rail but leaves the agent guessing what the call actually produces or confirms. Adequate but incomplete against the tool's modest complexity.

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% and both enum parameters are documented in-schema, so the baseline is 3. The description echoes the concepts behind 'gehaeuse' and the indoor/outdoor distinction but adds no syntax, allowed-value nuance, or guidance on how to fill 'identische_einsatzbedingungen' beyond what the schema already states.

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 name and text point at the topic (a model-specific closed luminaire housing claim, separated from indoor/outdoor suitability), but the German sentence is grammatically broken ('von Innenraum- oder Außeneignung trennen' dangles) and never states a concrete verb/action the tool performs. The English clause clarifies the intent to verify the specific enclosure condition, yet an agent still cannot tell precisely what the tool does operationally versus its siblings.

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?

The instruction 'Check the specific enclosure condition instead of generalizing an indoor-use claim' is a clear directive about when this tool is appropriate and what error it guards against. It stops short of naming an alternative sibling or an explicit when-not condition, so it is not a 5.

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