Skip to main content
Glama

getecoback-raumklima

arbeitsplatz_bildschirm_licht_brauchbare_feinprobe

Read-only

Für vorhandene Schreibtischlichtvarianten nur bereits erprobte Ergebnisse mit gleicher Bildschirmanforderung nach Strom vergleichen — Compare lighting draw among two setups whose task and screen visibility were checked.

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_brauchbar": "<a_brauchbar>",
      "b_brauchbar": "<b_brauchbar>",
      "a_wh": "<a_wh>",
      "b_wh": "<b_wh>",
      "tageslicht_bildschirm_konstant": "<tageslicht_bildschirm_konstant>"
    },
    "name": "arbeitsplatz_bildschirm_licht_brauchbare_feinprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_whYesGemessene Wh der Beleuchtung während derselben vollständigen Beobachtungsdauer.
b_whYesGemessene entsprechende Wh in Variante B.
a_brauchbarYesVariante A reichte in der Beobachtung für dieselbe Bildschirm- und Leseaufgabe.
b_brauchbarYesVariante B reichte in der Beobachtung für dieselbe Aufgabe.
tageslicht_bildschirm_konstantYesTageslicht, Bildschirmzustand und Messgrenze für beide Beobachtungen ähnlich.

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 safety and side effects are covered. The description adds one genuinely useful behavioral constraint beyond that: the comparison is only meaningful when usability and daylight/screen conditions were matched across both observations. It does not say what happens when a_brauchbar/b_brauchbar are false, nor what the comparison yields (delta, ratio, verdict), and there is no output schema to fill that gap.

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?

The content is short, but the German clause and the English clause say the same thing, effectively doubling length without adding information. The governing verb (vergleichen/compare) is buried after two long qualifiers, so the definition is not front-loaded on the action an agent is selecting the tool for.

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?

Five required parameters with full schema coverage plus a read-only annotation mean the input side is well covered and an agent can call the tool correctly. The remaining gap is the result: with no output schema, the description should state whether it returns a Wh difference, a ratio, or a usability-gated verdict. As written, an agent knows the preconditions but not what it will receive.

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 each of the five parameters carries a precise German description including units (Wh) and the observation-period constraint. The description adds only the umbrella rule that the two observations must share the same screen requirement, which the schema already implies through tageslicht_bildschirm_konstant. Baseline 3 is correct when the schema does the semantic work.

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 names a specific action (vergleichen/compare) on a specific resource (Stromverbrauch/Wh of two desk-lighting variants), not a restatement of the name. It also scopes the action to setups whose task and screen visibility were already verified, which separates it from the surrounding measurement/probe siblings. It stops short of naming any concrete alternative tool, so an agent must infer routing from context.

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?

"nur bereits erprobte Ergebnisse mit gleicher Bildschirmanforderung" is an explicit precondition for calling the tool and implicitly an exclusion (do not compare setups that were not proven usable under the same screen requirement). No alternative tool is named for the case where the precondition fails, so guidance is clear on context but not on fallback 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