Skip to main content
Glama

getecoback-climate-weather

schlafraum_arbeitswechsel_abkuehlung_zeitgruende

Read-only

Nach Arbeit im selben Raum Lüftung, Rückkehrtemperatur und Schlafbeginn koordinieren — Schedule a measured cooldown before switching a home office to a bedroom.

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": {
      "arbeitsende": "<arbeitsende>",
      "schlafbeginn": "<schlafbeginn>",
      "abkuehl_min": "<abkuehl_min>",
      "freie_vorbereitung_min": "<freie_vorbereitung_min>",
      "lueften_passend": "<lueften_passend>"
    },
    "name": "schlafraum_arbeitswechsel_abkuehlung_zeitgruende"
  }
}

Input Schema

NameRequiredDescriptionDefault
abkuehl_minYesGemessene Dauer bis zum selbst gewählten Ziel bei vergleichbarem Start.
arbeitsendeYesArbeitsende, Minuten seit Mitternacht.
schlafbeginnYesGeplanter Schlafbeginn am selben Tag.
lueften_passendYesSind Außenlage, sichere Fensterbedienung und Lüftungsmethode für diesen Versuch passend?
freie_vorbereitung_minYesZeit zum anschließenden Umräumen bei beendetem Lüften.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this a safe, closed-world read (readOnlyHint=true, openWorldHint=false), so the description only had to add compute behavior. It does not: what the tool actually returns or checks (a schedule? a feasibility verdict?) is never stated. The German 'koordinieren' hints at constraint reconciliation but stays uncommitted, and nothing about the lueften_passend gate is explained.

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 no padding, the scenario stated first and the action second. The German/English duplication is slightly redundant but reads as deliberate glossing rather than filler.

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 five required parameters, no output schema, and a computation-style tool, the description should at minimum say what is returned or how the inputs are reconciled; it does not. The annotation carries the safety profile and the schema carries the parameters, so nothing is fatal, but the model of the tool's output remains undefined for the agent.

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 every parameter is already documented in-schema; the description only echoes a few concepts (Lüftung, Rückkehrtemperatur, Schlafbeginn) and adds no constraint or unit guidance beyond them. Baseline 3 applies when the schema does the heavy lifting; it does not explain how the five required values interact (e.g. whether abkuehl_min plus freie_vorbereitung_min must fit between arbeitsende and schlafbeginn).

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 concrete action ('Schedule a measured cooldown') and the resources it coordinates (Lüftung, Rückkehrtemperatur, Schlafbeginn) in the specific scenario of converting a home office back into a bedroom. That is well beyond a restatement of the name, though it never distinguishes this from any of the many sibling Schlafraum/Arbeitsplatz tools.

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?

The only usage signal is the implied 'after working in the same room' scenario; there is no statement of when to call this versus a sibling like schlafraum_waermegradstunden_nacht or arbeitsplatz_raumwechsel_persoenliche_hitzepause, and no exclusions or prerequisites. An agent must guess which of the similarly named tools applies.

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