Skip to main content
Glama

getecoback-raumklima

fensterloser_raum_luftpfad_vorkuehlzeit

Read-only

Plant die Vorkühlzeit eines Nebenraums und den anschließenden Transfer getrennt — Back-plan adjacent-room cooldown and subsequent air-transfer stages.

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": {
      "start_tagesmin": "<start_tagesmin>",
      "ende_tagesmin": "<ende_tagesmin>",
      "vorkuehlung_min": "<vorkuehlung_min>",
      "transfer_min": "<transfer_min>"
    },
    "name": "fensterloser_raum_luftpfad_vorkuehlzeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
transfer_minYesAus eigener Beobachtung: anschließend benötigte Transferdauer in Minuten.
ende_tagesminYesEnde des geplanten Wegs als Tagesminute desselben Tages in Minuten.
start_tagesminYesBeginn der gemessenen kühlen Außenphase als Tagesminute in Minuten.
vorkuehlung_minYesAus eigener Beobachtung: Zeit bis der Nebenraum den Zielzustand hatte in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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 is not contradicting them. Beyond that it only repeats the 'getrennt' framing and says nothing about what is computed, whether the returned plan is absolute daily minutes or deltas, or how the two stage values relate. For a planning/computation tool with no output schema, that is a substantial disclosure gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence, front-loaded with the German statement of purpose, which is good. The English half is a flat restatement rather than added information, so roughly half the text does not earn its place, and the phrase 'Back-plan' is awkward enough to add ambiguity rather than clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All four required parameters are fully documented in the schema, so input-side completeness is fine. But for a tool whose whole job is to plan two stages, there is no output schema and the description never indicates what comes back, leaving the agent unable to predict the result shape or how to consume the response.

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 the schema itself carries all four parameters including their minute units and the 0–1440 bounds. The description adds the conceptual split between the cooldown stage and the transfer stage, which loosely maps to vorkuehlung_min and transfer_min, but contributes no format, ordering, or validity detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific object (Vorkühlzeit eines Nebenraums) and a second stage (anschließenden Transfer) plus the notion of planning them separately, which is more than a restatement of the name. However, what the tool actually produces — a schedule, a duration estimate, a verdict — is never stated, and nothing distinguishes it from the sibling fensterloser_raum_waermeabfuhr beyond the word 'Vorkühlzeit'. The purpose is inferable but not crisp.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or prerequisite guidance of any kind. The word 'getrennt' hints that the two stages are handled as separate items, but the agent is not told under what circumstances to pick this tool over the related windowless-room and air-path siblings.

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