Skip to main content
Glama

getecoback-raumklima

sommerluft_kuehler_und_trockener_fensterwahl

Read-only

Zwei gemessene Lüftungsfenster mit Abkühlungs- und Feuchteziel vergleichen — Compare two outdoor-air samples when cooling and drying both matter.

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": {
      "innen_c": "<innen_c>",
      "innen_tau_c": "<innen_tau_c>",
      "wand_c": "<wand_c>",
      "a_c": "<a_c>",
      "a_tau_c": "<a_tau_c>",
      "b_c": "<b_c>",
      "b_tau_c": "<b_tau_c>",
      "reserve_c": "<reserve_c>"
    },
    "name": "sommerluft_kuehler_und_trockener_fensterwahl"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_cYesAußentemperatur bei Fenster A.
b_cYesAußentemperatur bei Fenster B.
wand_cYesKälteste gemessene Oberfläche im betrachteten Raum.
a_tau_cYesAußentaupunkt A aus der gleichzeitigen Außenmessung.
b_tau_cYesAußentaupunkt B aus der gleichzeitigen Außenmessung.
innen_cYesAktuelle Raumlufttemperatur.
reserve_cYesEigene konservative Reserve zur kältesten Wand, berücksichtigt die Messunsicherheit.
innen_tau_cYesAktueller Innentaupunkt.

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, so the agent knows this is a pure offline computation. The description adds that the two windows must be 'gemessene' (measured) samples, which is genuinely useful context beyond the schema's field labels. It stops short of saying what is actually computed for each window (condensation margin against the wall, cooling verdict) or how 'reserve_c' tips the comparison, so the behavioral picture remains partial.

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 front-loaded clause with the verb first, no filler, and the decision criteria stated last. The bilingual duplication is mild redundancy but arguably serves the mixed-language naming convention of the catalog.

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?

For an 8-required-parameter computation tool with no output schema, the description never states what the caller receives back — a ranking of A vs B, a per-window verdict, or a margin value. Nor does it explain how the wall temperature and reserve combine into a risk decision. It is adequate to know when to call it, but incomplete for predicting the result.

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 parameter is documented in German, including that the dew points come 'aus der gleichzeitigen Außenmessung'. The description's only added meaning is that both samples are measured ventilation windows, which the schema largely already conveys. With the schema doing the heavy lifting, the baseline of 3 applies.

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 verb ('Compare' / 'vergleichen') and a specific resource ('two measured ventilation windows' / 'zwei gemessene Lüftungsfenster'), plus the two evaluation criteria: cooling and drying/moisture target. An agent can tell this is a pairwise A-vs-B decision tool rather than a single-sample lookup. It does not name or exclude any sibling, so differentiation stops at the resource level.

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?

'when cooling and drying both matter' gives an implied trigger condition, and 'gemessene' implies real simultaneous measurements rather than forecasts. However there is no explicit when-not guidance, no mention of prerequisites (e.g. that wall temperature must be measured for the same room), and no named alternative for the case where only one goal matters.

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