Skip to main content
Glama

getecoback-raumklima

abluftfenster_schlussbeleg_vor_abwesenheit

Read-only

Prüft ob der dokumentierte Fensterschluss vor dem tatsächlichen Verlassen des Raums lag — Compare recorded normal window closure with the start of an absence.

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": {
      "abwesend_ab_min": "<abwesend_ab_min>",
      "schluss_min": "<schluss_min>",
      "schluss_belegt": "<schluss_belegt>"
    },
    "name": "abluftfenster_schlussbeleg_vor_abwesenheit"
  }
}

Input Schema

NameRequiredDescriptionDefault
schluss_minYesZeitpunkt des beobachteten regulären Fensterschlusses, wenn belegt in Minuten.
schluss_belegtYesWar der normale Fensterschluss tatsächlich beobachtet und im selben Zeitbezug dokumentiert?
abwesend_ab_minYesBeginn der beobachteten Abwesenheit ab Protokollbeginn in Minuten.

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 safety is covered. The description adds that this is a comparison check over documented/observed data, but says nothing about behavior when schluss_belegt is false (no closure recorded), whether a missing record yields a failure or an unknown verdict, or what the check returns.

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?

One compact sentence (in German with an English gloss) that is front-loaded on the check being performed. The bilingual duplication is slightly redundant but costs little and aids clarity.

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?

There is no output schema, so the description carries the burden of explaining what the check returns — a boolean match, a verdict, or a delta — and it does not. Combined with no guidance on the undocument case, the definition is adequate but leaves an agent guessing about the result shape.

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 three parameters are already documented in the schema, establishing a baseline of 3. The description confirms the relationship between the closure timestamp and the absence start, but adds no format, unit, or edge-case meaning beyond what the schema provides.

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?

A clear verb-plus-resource statement: it checks whether the documented window closure happened before the room was actually left, and it names the two quantities being compared. It doesn't name a sibling tool to differentiate from, but the comparison itself is specific enough that an agent knows what question this tool answers.

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?

Usage is implied by the comparison semantics — call it to verify a closure-before-absence ordering — but there is no explicit statement of when to use it, when not to, or which of the many similarly named sibling tools to prefer. The agent must infer context from the name and parameters.

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