Skip to main content
Glama

getecoback-raumklima

nachtlueftung_sensorreaktion_messzeiten_abgleichen

Read-only

Bei einer kurzen Kühlphase Messzeiten gegen die dokumentierte Fühler-Reaktionszeit abgleichen — Decide whether a short cooling record gives a moved sensor time to settle.

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": {
      "aussen_gesetzt_min": "<aussen_gesetzt_min>",
      "innen_gesetzt_min": "<innen_gesetzt_min>",
      "vergleich_min": "<vergleich_min>",
      "aussen_ruhe_min": "<aussen_ruhe_min>",
      "innen_ruhe_min": "<innen_ruhe_min>"
    },
    "name": "nachtlueftung_sensorreaktion_messzeiten_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
vergleich_minYesMinute für die gemeinsame Ablesung.
innen_ruhe_minYesEntsprechende Zeit für das Innengerät.
aussen_ruhe_minYesBenötigte Beruhigungszeit laut Anleitung oder eigener stabiler Probe außen.
innen_gesetzt_minYesMinute des Aufstellens des Innenfühlers auf derselben Achse.
aussen_gesetzt_minYesMinute auf gemeinsamer Zeitachse seit Aufstellen des Außenfühlers am endgültigen Ort.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-world read operation. The description adds that the tool is used to decide whether the sensor has settled, but it does not explain the result format or any operational constraints beyond that.

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?

The definition is short and front-loads the domain context before stating the decision purpose. The bilingual phrasing repeats the same idea, but it remains efficient rather than padded.

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?

The schema fully documents the inputs and annotations cover read-only behavior. However, because there is no output schema, the description should say more about what the comparison returns or how the decision is expressed.

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?

All five parameters have complete schema descriptions, including the set, rest, and comparison minutes. The description adds no parameter-level detail beyond the schema, so the baseline of 3 is appropriate.

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 (Messzeiten abgleichen) against a documented sensor reaction time and frames it around a short cooling phase. It is clear enough to distinguish this as a sensor-settling check, though it does not explicitly contrast with sibling tools.

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

Usage Guidelines4/5

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

It gives a clear usage context: during a short cooling phase, to decide whether a moved sensor had time to settle. It does not state when not to use it or name a specific alternative tool, so it falls short of full routing 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