Skip to main content
Glama

getecoback-raumklima

heizmeldung_sollwertzeit_messbezug

Read-only

Prüfen, ob ein gemeldeter Raumwert zu dem damals eingestellten Heizprogramm gehört — Reconcile an indoor reading with the active heating setpoint.

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": {
      "beobachtung_min": "<beobachtung_min>",
      "wechsel_min": "<wechsel_min>",
      "sollwert_c": "<sollwert_c>",
      "gemessen_c": "<gemessen_c>",
      "programm_abgeglichen": "<programm_abgeglichen>"
    },
    "name": "heizmeldung_sollwertzeit_messbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
gemessen_cYesGemessene Raumluft in °C.
sollwert_cYesZur Messung angenommener Sollwert in °C.
wechsel_minYesLetzter Sollwertwechsel als Minute desselben Tages.
beobachtung_minYesMesszeit als Minute des beobachteten Tages.
programm_abgeglichenYesZeitprogramm und mögliche manuelle Änderung für den Zeitpunkt tatsächlich geprüft?

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 the safety profile is covered. The description adds that the operation reconciles a reading against a historical setpoint, but it does not explain tolerance, how programm_abgeglichen=false is treated, or what result to expect. With annotations present, this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence in German plus a concise English translation, front-loaded with the check and the resource. There is no filler, and every phrase supports the task.

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

Completeness2/5

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

For a five-parameter reconciliation tool with no output schema, the description omits return semantics and does not explain the reconciliation criteria, such as how the measurement time and last setpoint change are compared. The schema covers inputs and annotations cover safety, but an agent still lacks enough to interpret the result correctly.

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 coverage is 100% and all five parameters have descriptions, so the schema carries the parameter meaning. The description refers generally to a reported room value and setpoint but adds no syntax, boundaries, or interpretation beyond the schema. Baseline 3 applies.

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 German sentence names a specific check: whether a reported room value belongs to the heating program set at that time, and the English gloss reinforces 'reconcile an indoor reading with the active heating setpoint.' It does not explicitly contrast with the sibling heizmeldung_raumabdeckung_zusammenfassen, so 4 rather than 5.

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?

No when-to-use, when-not-to-use, prerequisites, or alternatives are given. The description only states what the check does, leaving the agent to infer that it should be called for heating-report reconciliation.

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