Skip to main content
Glama

getecoback-raumklima

led_lumen_candela_lux_bezugsraum_vergleichen

Read-only

Zwei Lichtangaben nur bei gleicher Messgröße und vergleichbarem Messbezug zahlenmäßig gegeneinander halten — Preserve photometric quantity and scope rather than converting one number blindly.

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": {
      "a_wert": "<a_wert>",
      "b_wert": "<b_wert>",
      "a_groesse": "<a_groesse>",
      "b_groesse": "<b_groesse>",
      "vergleichsbedingung_gleich": "<vergleichsbedingung_gleich>"
    },
    "name": "led_lumen_candela_lux_bezugsraum_vergleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_wertYesErster ausgewiesener Lichtwert in der angegebenen Einheit.
b_wertYesZweiter ausgewiesener Lichtwert in der angegebenen Einheit.
a_groesseYesEinheit samt Bezug des ersten Originalwerts.
b_groesseYesEinheit samt Bezug des zweiten Originalwerts.
vergleichsbedingung_gleichYesGleiche Einstellung, Messart und bei Lux auch gleiche Fläche, Distanz und Ausrichtung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 structurally. The description adds one genuinely useful behavioral fact — that no unit conversion happens and quantity/scope are preserved — but says nothing about the comparison result, tolerances, or what happens when the quantities differ.

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 tight sentence with the precondition front-loaded before the instruction, plus a short bilingual gloss. Every clause carries meaning; the em-dash gloss is slightly redundant for a German-reading agent but not wasteful.

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?

For a read-only, annotation-covered tool with full schema coverage and no output schema, the definition supplies what an agent needs to decide and call correctly. Only the returned comparison result is left unspecified, which is a minor gap given five fully documented required parameters.

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 the enum values (lm_360, lm_120, lm_90, cd_spitze, lx_messpunkt, offen) and the vergleichsbedingung_gleich boolean are already documented in the schema. The description reinforces why a_groesse/b_groesse must align but adds no new syntax or format detail.

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?

States a specific action (zwei Lichtangaben zahlenmäßig gegeneinander halten) on a specific resource (photometric values), and immediately narrows it with the condition of identical measurand and comparable reference. It is distinguishable from conversion-style siblings, though it never names an alternative tool explicitly.

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?

Gives a clear precondition for use ('nur bei gleicher Messgröße und vergleichbarem Messbezug') and implicitly warns against blind conversion. It lacks an explicit 'use X instead when...' routing to a conversion tool, so it stops short of full alternative guidance.

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