Skip to main content
Glama

getecoback-raumklima

vorhang_sonnenlauf_waerme_licht_gemeinsame_probe

Read-only

Prüfe, ob die beschattete Nachprobe beide eigenen Ziele am selben Nutzplatz gleichzeitig trifft — Check simultaneous heat and daylight goals in a measured shading trial

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": {
      "vorher_lux": "<vorher_lux>",
      "nachher_lux": "<nachher_lux>",
      "innen_nach_c": "<innen_nach_c>",
      "mindest_lux": "<mindest_lux>",
      "maximal_c": "<maximal_c>",
      "vergleichsaufbau_fix": "<vergleichsaufbau_fix>"
    },
    "name": "vorhang_sonnenlauf_waerme_licht_gemeinsame_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
maximal_cYesPersönlich gewählte obere Raumtemperatur
vorher_luxYesVorherige Beleuchtungsstärke am Nutzplatz
mindest_luxYesPersönlich gewählter Lichtwert
nachher_luxYesSpätere Beleuchtungsstärke am gleichen Platz, zeitgleich zum Wärmeprotokoll
innen_nach_cYesZeitgleiche Raumtemperatur am Nutzplatz
vergleichsaufbau_fixYesKunstlicht, Platz, Messausrichtung und Messzeitpunkt sind dokumentiert

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 and the description need only add domain behavior. It does add a meaningful constraint – the two measurements must be simultaneous at the same use location – which is real context beyond the annotations. However, with no output schema it never says what the check yields (pass/fail verdict, per-goal breakdown, or an error when goals conflict), leaving the most important behavioral question open.

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?

One compact sentence with the core condition front-loaded, and the em-dash English gloss makes the intent scannable for a non-German reader. The German and English halves are near-duplicates, which is mild redundancy but defensible for a bilingual definition.

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?

Six required numeric/boolean parameters are fully documented in the schema, so the input side is complete. The gaps sit on the output side: no output schema exists and the description never indicates the shape of the verdict (two booleans, a combined result, or a diagnostic when one goal fails while the other passes). For a judgment-style check tool, that is a noticeable omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description adds a small amount on top by emphasizing that the heat and daylight readings must come from the same use location at the same moment, which frames how 'nachher_lux' and 'innen_nach_c' relate. It adds no units or thresholds guidance beyond the schema but does not need to.

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 verb ('Prüfe'/'Check') and a specific composite condition: whether a shaded follow-up measurement meets BOTH a heat goal and a daylight goal at the same use location at the same time. The phrase 'beschattete Nachprobe' scopes it to a follow-up measurement after a shading intervention, which separates it from ordinary measurement-series siblings. It stops short of naming a specific sibling to defer to.

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?

Usage is only implied: the agent can infer this is for the joint heat+light evaluation step of a shading trial, and the schema's 'vergleichsaufbau_fix' hints at a documented-setup precondition. There is no explicit when-to-use/when-not, no mention of which sibling handles single-goal checks, and no statement of prerequisites beyond the vague 'measured shading trial'.

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