Skip to main content
Glama

getecoback-climate-weather

lueftung_belegungswechsel_zeitfenster

Read-only

Prüft wie viel freie Lüftungszeit vor der nächsten Raumnutzung tatsächlich bleibt — Check a vacant ventilation interval before the next occupancy.

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": {
      "nutzungsende_min": "<nutzungsende_min>",
      "lueftungsstart_min": "<lueftungsstart_min>",
      "folgetermin_min": "<folgetermin_min>",
      "zielzeit_min": "<zielzeit_min>"
    },
    "name": "lueftung_belegungswechsel_zeitfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielzeit_minYesSelbst gewählte Lüftungsdauer in Minuten.
folgetermin_minYesBeginn der folgenden Nutzung als Tagesminute in Minuten.
nutzungsende_minYesEnde der ersten Nutzung als Minute desselben Tages ab Mitternacht in Minuten.
lueftungsstart_minYesGeplanter Lüftungsstart als Tagesminute in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety is covered. The description adds that the tool reports what *actually* remains, implying the result may be less than the requested duration, but it never says what the return looks like or what happens when the interval is too short for zielzeit_min.

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, front-loaded clauses that lead with the operation and the scenario. The only waste is the fully duplicated German and English rendering of the same sentence, which adds length without new information.

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 four required numeric parameters and no output schema, the description must carry the meaning of the result, and it only hints at it ('wie viel ... tatsächlich bleibt'). An agent can call it correctly but cannot predict whether it returns remaining minutes, a boolean feasibility verdict, or a deficit.

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 of the four minute values is documented in the schema, so the baseline of 3 applies. The description adds no syntax, ordering, or interaction detail beyond the schema, such as how zielzeit_min is compared against the computed gap.

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 operation (checking remaining free ventilation time) on a specific resource (the interval between end of use and the next occupancy). It is clearly a computation tool about room ventilation scheduling. It stops short of contrasting itself with the many sibling '*_zeitfenster' tools, so an agent must infer the distinction from the domain nouns alone.

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 description states what is checked but gives no explicit when-to-use condition, no prerequisites, and no pointer to an alternative sibling tool. The phrase 'vor der nächsten Raumnutzung' sets the scenario, but that is context rather than guidance.

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