Skip to main content
Glama

getecoback-climate-weather

led_lichtstrom_und_watt_vergleich

Read-only

LED-Angebote bei gleichem vorgesehenem Lichtstrom anhand der Lumen-pro-Watt-Angabe einordnen. — Compare lamp efficacy only for alternatives that deliver comparable intended light.

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": {
      "lumen_a": "<lumen_a>",
      "lumen_b": "<lumen_b>",
      "watt_a": "<watt_a>",
      "watt_b": "<watt_b>",
      "lichtaufgabe_gleich": "<lichtaufgabe_gleich>",
      "toleranz_prozent": "<toleranz_prozent>"
    },
    "name": "led_lichtstrom_und_watt_vergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
watt_aYesDeklarierte Leistungsaufnahme A in W.
watt_bYesDeklarierte Leistungsaufnahme B in W.
lumen_aYesDeklarierter Lichtstrom A in lm.
lumen_bYesDeklarierter Lichtstrom B in lm.
toleranz_prozentYesMaximale akzeptierte Differenz des Lichtstroms relativ zu A in Prozent.
lichtaufgabe_gleichYesLampen sollen dieselbe Lichtaufgabe erfüllen und Abstrahlung ist vergleichbar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 only that offers are to be 'eingeordnet' — it does not indicate what the evaluation returns (a ratio, a ranking, a verdict), how tolerance is applied, or what happens when the tolerance is exceeded.

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?

Two short sentences, with the core action front-loaded and the comparability constraint immediately after. The English sentence is essentially a translation of the German one, so it adds length without new information, but the total size remains small.

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 six required parameters and no output schema, the description should convey what the comparison produces and how the tolerance percentage influences the result. It establishes the input discipline but leaves the returned evaluation entirely unspecified.

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 all six parameters are already documented in the schema with units and bounds. The description adds no syntax, unit or interpretation detail beyond that, which matches the baseline of 3 when the schema carries the load.

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 states a specific action (compare/rank LED offers by lumens-per-watt) and a specific resource (declared luminous flux and wattage of two lamps). It is clearly distinguishable from the heating, airflow and humidity siblings, though it does not name any sibling it might be confused with.

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?

It gives an explicit applicability condition — compare only alternatives that deliver a comparable intended light output — which functions as a when-not-to-use rule. However, no alternative tool or fallback path is named for the case where the light tasks are not comparable, and the condition largely mirrors the required boolean parameter.

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