Skip to main content
Glama

getecoback-raumklima

winterfenster_oberflaeche_erholt_sich_spaeter

Read-only

Nach einer Lüftung getrennt prüfen, ob Raumluft und kalte Oberfläche wieder ihr Ausgangsniveau erreichen — Verify separate air and surface recovery instead of extrapolating from a warm room.

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": {
      "luft_vorher_c": "<luft_vorher_c>",
      "wand_vorher_c": "<wand_vorher_c>",
      "luft_spaeter_c": "<luft_spaeter_c>",
      "wand_spaeter_c": "<wand_spaeter_c>",
      "toleranz_c": "<toleranz_c>",
      "gleiche_stellen": "<gleiche_stellen>"
    },
    "name": "winterfenster_oberflaeche_erholt_sich_spaeter"
  }
}

Input Schema

NameRequiredDescriptionDefault
toleranz_cYesEigene Vergleichstoleranz für die Messgeräte in °C.
luft_vorher_cYesMessung in der Raummitte vor dem Öffnen.
wand_vorher_cYesMessung an einer markierten kalten Stelle vor dem Öffnen.
luft_spaeter_cYesSpätere Luftmessung bei wieder geschlossenem Fenster.
wand_spaeter_cYesSpätere Oberflächenmessung an derselben Stelle.
gleiche_stellenYesBestätigt, dass Messorte, Oberfläche und Verfahren unverändert sind?

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, consistent with a pure input-based check. The description reinforces the closed-world, non-mutating nature by framing it as a verification of recovery, but says nothing about how tolerance is applied or what happens if the measurement sites changed (gleiche_stellen).

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?

Two short clauses with the condition front-loaded and no filler. The German/English mirror is mildly redundant but serves as an explicit gloss and does not obscure the intent.

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?

All six required parameters are fully described in the schema and the tool is a read-only computation, so the essentials are covered. Still, with no output schema, the description never indicates what the check produces (verdict vs. deviation values) or how a failed gleiche_stellen confirmation is treated.

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 six parameters are already documented. The description adds modest value by stressing 'getrennt' (air and surface evaluated separately) and 'Ausgangsniveau' (baseline = the 'vorher' readings), 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 description names a specific check (whether room air and cold surface separately return to baseline after ventilation) and explicitly contrasts it with extrapolating from a warm room. The verb+resource is clear, though it does not name a sibling such as fenster_oberflaeche_taucheck to sharpen the boundary.

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?

Timing context is given ('Nach einer Lüftung') and the method caveat ('statt vom warmen Raum zu extrapolieren') implies when this check is appropriate. However, no alternative tool or when-not condition is named, so the agent must infer routing from the sibling catalog.

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