Skip to main content
Glama

getecoback-climate-weather

fensterloser_raum_waermeabfuhr

Read-only

Prüfen, ob ein Klimagerät in einem fensterlosen Raum Wärme wirklich nach außen abführen kann — Identify viable heat rejection for a windowless 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": {
      "aussenanschluss": "<aussenanschluss>",
      "freigabe": "<freigabe>"
    },
    "name": "fensterloser_raum_waermeabfuhr"
  }
}

Input Schema

NameRequiredDescriptionDefault
freigabeYesIst die konkrete Durchführung laut Hersteller und für den Einbauort zulässig?
aussenanschlussYesVorgesehene Wärmeabfuhr. Direkter Außenanschluss und zugelassene Außenführung zählen als Außenweg.

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 and the description carries a lighter burden. It adds the evaluative framing (a feasibility verdict on heat rejection) but says nothing about what the result looks like, how the two inputs combine into a decision, or any limits. Adequate but thin beyond the annotations.

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 sentence with the check stated first, followed by a parallel English rendering for bilingual readers. No filler, though the duplicated translation is slightly redundant for a monolingual reader.

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?

With only two fully documented enum parameters and annotations covering the read-only profile, the main remaining gap is what the tool returns — a verdict on viability is implied but never stated, and there is no output schema to fall back on. For a decision/assessment tool, that omission leaves the definition short of complete.

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% and both parameters have German enum descriptions that fully explain 'aussenanschluss' (including that direct outdoor connection and approved outdoor routing both count as an outdoor path) and 'freigabe' (manufacturer/site approval). The description adds no further meaning, so the baseline 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 states a specific verb ('Prüfen') and a specific subject: whether an air-conditioning unit in a windowless room can actually reject heat to the outside. That is far more than a restatement of the name and lets an agent recognise the task. It stops short of distinguishing itself from nearby siblings such as abluftplatte_lochposition_pruefen or geraet_wahl.

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?

The windowless-room scenario implies when the tool applies, but there is no explicit when-to-use or when-not-to-use statement, no prerequisites, and no pointer to an alternative tool. The agent must infer the boundary from the purpose sentence alone.

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