Skip to main content
Glama

getecoback-raumklima

arbeitsplatz_lichtmessung_bildschirm_lichtquelle_abgrenzen

Read-only

Die bestehende Lichtmessung am Tisch nur dann als Beleuchtungsreferenz verwenden, wenn die Bildschirmphase als eigene Quelle abgegrenzt ist — Compare controlled black-screen and reference-image readings at a fixed work surface.

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": {
      "dunkelbild_lux": "<dunkelbild_lux>",
      "referenzbild_lux": "<referenzbild_lux>",
      "toleranz_lux": "<toleranz_lux>",
      "raumlicht_konstant": "<raumlicht_konstant>"
    },
    "name": "arbeitsplatz_lichtmessung_bildschirm_lichtquelle_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
toleranz_luxYesKleinster eigener unterscheidbarer Messabstand in Lux.
dunkelbild_luxYesGemessene Beleuchtungsstärke am Schreibtisch mit dunklem Referenzbild.
referenzbild_luxYesEntsprechende Messung am gleichen Ort mit dokumentiertem Referenzbild.
raumlicht_konstantYesTageslicht, Lampen, Monitorposition und Beobachtungspunkt blieben in beiden Proben gleich.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 this is a conditional comparison rather than a raw read, but it never states what happens when the delineation condition fails (error vs. negative verdict) or how the toleranz_lux threshold is applied. That leaves the tool's actual behavior underspecified for a validation-style operation.

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?

There is little wasted text, but the structure is inverted: it leads with a usage precondition and only reveals the action after an em dash, and the German clause is syntactically heavy. Leading with 'Compare ... readings' would make the definition scannable on first pass.

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?

Four required numeric/boolean parameters are well documented and there is no output schema, so the description must carry the return-value burden — but it never indicates whether the result is a lux delta, a pass/fail verdict, or a reference-validity flag. For a read-only comparison tool this is an adequate but incomplete definition.

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 coverage is 100% with per-parameter descriptions, so the schema already carries the load and the baseline is 3. The description frames the two lux readings as a black-screen vs. reference-image pair at one fixed location, which reinforces their relationship but adds no format or tolerance semantics beyond the schema.

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 second clause gives a concrete verb plus resource — 'Compare controlled black-screen and reference-image readings at a fixed work surface' — which maps cleanly onto the dunkelbild_lux/referenzbild_lux parameters. It does not differentiate against the closely named sibling arbeitsplatz_bildschirm_licht_brauchbare_feinprobe, so an agent must guess which screen-light probe to pick. The purpose is clear but the leading clause buries it behind a precondition.

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 opening sentence is an explicit when-to-use gate: only treat the desk measurement as an illumination reference if the screen phase is delineated as its own source. It also implies the constancy precondition (raumlicht_konstant). It stops short of naming when to use an alternative tool instead, so it is strong context without explicit routing.

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