Skip to main content
Glama

getecoback-climate-weather

led_arbeitsflaeche_drei_luxpunkte_gegen_basis

Read-only

In einem dokumentierten Leuchtenvergleich prüfen, ob die zusätzliche Beleuchtung nur den Mittelpunkt verbessert — Check a matched centre-and-edge lux comparison before treating a spot as an even task 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": {
      "basis_mitte_lx": "<basis_mitte_lx>",
      "basis_rand_a_lx": "<basis_rand_a_lx>",
      "basis_rand_b_lx": "<basis_rand_b_lx>",
      "test_mitte_lx": "<test_mitte_lx>",
      "test_rand_a_lx": "<test_rand_a_lx>",
      "test_rand_b_lx": "<test_rand_b_lx>",
      "zusatzziel_lx": "<zusatzziel_lx>",
      "gleiche_messpunkte_und_umgebung": "<gleiche_messpunkte_und_umgebung>"
    },
    "name": "led_arbeitsflaeche_drei_luxpunkte_gegen_basis"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_mitte_lxYesMit Zusatzlicht gemessener Wert an derselben Mitte.
zusatzziel_lxYesEigene Mindestverbesserung, die an jedem dieser Punkte benötigt wird.
basis_mitte_lxYesStabile Beleuchtungsstärke ohne Zusatzlicht in der Mitte.
test_rand_a_lxYesMit Zusatzlicht gemessener Wert an demselben Randpunkt A.
test_rand_b_lxYesMit Zusatzlicht gemessener Wert an demselben Randpunkt B.
basis_rand_a_lxYesDieselbe Referenz an Randpunkt A.
basis_rand_b_lxYesDieselbe Referenz an Randpunkt B.
gleiche_messpunkte_und_umgebungYesFläche, Messpunkte, Ausrichtung, Messgerät und getrennte Fremdbeleuchtung vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 that the comparison must be 'matched' and documented, which hints at the comparability precondition, but it does not say what verdict is produced, what happens when gleiche_messpunkte_und_umgebung is false, or how the per-point requirement is enforced.

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 compact sentence, front-loaded with the intent before the decision context. The German/English duplication is redundant but short, and no sentence is wasted.

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 an eight-required-parameter computational tool with no output schema, the description is only barely sufficient: it explains the comparison concept but not the returned verdict, the failure mode for incomparable measurements, or how the custom improvement threshold is applied. Richer behavioral detail would be expected here.

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 eight parameters are already documented in the schema. The description only reinforces the centre-and-edge matching concept and adds no new detail on syntax, units beyond lx, or the role of zusatzziel_lx – baseline 3 is appropriate.

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?

Both language versions state a specific verb (prüfen/check) and a concrete resource: a matched centre-and-edge lux comparison against a baseline. The purpose is unmistakable, but the description never names which sibling tool to use for related lighting questions (e.g. the Lumen/Candela/Lux or half-value-angle tools), so sibling differentiation rests on the name alone.

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?

The clause 'before treating a spot as an even task light' gives an implied decision context for invoking the tool. However, there is no explicit when-not guidance, no prerequisites, and no named alternative for related measurements – an agent must infer the usage boundary.

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