Skip to main content
Glama

getecoback-climate-weather

kwl_winter_rueckwaerme_messquote

Read-only

Die beobachtete zuluftseitige Temperaturänderung der Wohnraumlüftung im Winter einordnen — Estimate an apparent single-point supply-air heat-recovery ratio.

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": {
      "aussen_c": "<aussen_c>",
      "abluft_c": "<abluft_c>",
      "zuluft_c": "<zuluft_c>",
      "stabil_ohne_zusatz": "<stabil_ohne_zusatz>"
    },
    "name": "kwl_winter_rueckwaerme_messquote"
  }
}

Input Schema

NameRequiredDescriptionDefault
abluft_cYesTemperatur der aus den Räumen eintretenden Abluft. In °C.
aussen_cYesTemperatur der eintretenden Außenluft. In °C.
zuluft_cYesTemperatur der Zuluft nach dem Wärmetauscher. In °C.
stabil_ohne_zusatzYesStabiler Betrieb mit aktiver Rückgewinnung, ohne Zusatzheizung, Frostschutzumschaltung oder offenen Bypass?

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 safety profile is covered. The description contributes the useful epistemic caveat 'apparent single-point' ratio, signalling the result is an estimate rather than a measured efficiency. It does not say what the tool returns when stabil_ohne_zusatz is false, nor whether an invalid-condition result is flagged.

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, front-loaded with the German purpose statement and immediately glossed in English. The bilingual duplication is slightly redundant, but nothing is padded and no sentence is wasted.

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?

There is no output schema, so the description must carry the return-value burden, and it only vaguely indicates a 'ratio' without stating scale, range, or interpretation. Combined with silence on the unstable-operation case (stabil_ohne_zusatz=false), the definition is adequate but leaves real gaps for a four-parameter computation tool.

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 coverage is 100%, with units (°C), bounds, and a fully spelled-out boolean condition, so the schema already carries the parameter burden. The description adds no interpretation beyond naming the supply-air temperature change as the observed quantity, which is the expected baseline when the schema is this complete.

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 English clause gives a specific verb and resource: 'Estimate an apparent single-point supply-air heat-recovery ratio', scoped to winter operation of the Wohnraumlüftung. It is clear what the tool computes, but it never distinguishes itself from the seasonal sibling kwl_sommerbypass_kuehlgewinn_probe, so the agent must infer the split from the word 'Winter' alone.

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 through the winter qualifier and the requirement that stabil_ohne_zusatz be true for a meaningful reading. There is no explicit statement of when to call this versus the summer-bypass counterpart, and no note about what to do when the system is not in stable recovery mode.

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