Skip to main content
Glama

getecoback-raumklima

nachtlueften_oeffnungslog_unterbrechungen

Read-only

Tatsächliche Offenzeit aus wetterbedingten Unterbrechungen im Nachtprotokoll berechnen — Audit usable open-window time after recorded disruptions.

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": {
      "geplant_min": "<geplant_min>",
      "regenpause_min": "<regenpause_min>",
      "weitere_pause_min": "<weitere_pause_min>",
      "gemeinsam_min": "<gemeinsam_min>"
    },
    "name": "nachtlueften_oeffnungslog_unterbrechungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
geplant_minYesLänge des zu protokollierenden Lüftungsblocks in Minuten.
gemeinsam_minYesÜberlappende Minuten, die in beiden Pausen enthalten sind.
regenpause_minYesMinuten, in denen das Fenster beobachtet wegen Regen geschlossen war.
weitere_pause_minYesWeitere beobachtete Schließzeit, etwa bei Böen oder warmem Außenwert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 usefully confirms this is a pure derivation from recorded data rather than a live measurement. It does not disclose the arithmetic itself (how overlapping minutes interact, whether the result is clamped at zero) or the unit of the returned value, which are the behaviors an agent would actually want here.

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 states the computed quantity first, then its practical purpose, with no filler. The German/English duplication is mild redundancy but keeps the definition short and readable.

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

Completeness4/5

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

For a four-number deterministic calculator with no output schema and fully covered parameters, the description names the computed quantity well enough for correct invocation. It is slightly thin on what the return value looks like (a single figure in minutes) and on how the overlap term is applied, but nothing essential is missing.

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 all four numeric parameters are already documented in the schema, including the overlap parameter gemeinsam_min. The description adds no interpretation beyond that, which is the expected baseline when the schema carries the full burden.

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 pairs a specific verb ("berechnen" / "calculate") with a specific output resource ("Tatsächliche Offenzeit … im Nachtprotokoll", "usable open-window time"), so the agent knows this is a derivation tool, not a logger. It does not contrast itself with related siblings such as nachtlueften_windmittel_und_boeen, so differentiation relies on the name 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?

The phrase "Audit usable open-window time after recorded disruptions" implies the context of use — reconciling a night-ventilation record that already contains logged interruptions. There is no explicit when-not guidance or pointer to a sibling for the case where no disruptions were recorded, leaving the boundary implicit.

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