Skip to main content
Glama

getecoback-climate-weather

thermostat_anforderungen_geraetereaktion_protokoll

Read-only

Thermostatanforderungen und gemessene Heizstarts unterscheiden, bevor eine ausbleibende Wirkung am Nutzplatz eingeordnet wird — Audit matched requests, documented lockouts and unexplained starts.

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": {
      "anforderungen": "<anforderungen>",
      "passende_starts": "<passende_starts>",
      "belegte_sperren": "<belegte_sperren>",
      "starts_gesamt": "<starts_gesamt>",
      "gleiche_uhr": "<gleiche_uhr>"
    },
    "name": "thermostat_anforderungen_geraetereaktion_protokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
gleiche_uhrYesSind Uhrenabgleich, Beobachtungszeit und Eindeutigkeit der Zuordnung bestätigt?
anforderungenYesEindeutige protokollierte Heizanforderungen im gemeinsamen Beobachtungsfenster.
starts_gesamtYesAlle separaten beobachteten Starts im selben Fenster.
belegte_sperrenYesWeitere Anforderungen ohne Start mit protokollierter Sperre oder belegt bereits laufendem Gerät.
passende_startsYesErfolgreich eindeutig zugeordnete Heizstarts, jeweils höchstens einer pro Anforderung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 this is an audit reconciling matched requests, documented lockouts and unexplained starts, which clarifies intent beyond the annotations. It says nothing about what is returned or how the reconciliation is expressed, and with no output schema that gap is left entirely open.

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

Conciseness3/5

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

The German clause is dense and syntactically convoluted, and the English gloss largely duplicates it rather than extending it, so half the text is redundant. There is no wasted filler, but the bilingual split spends words without adding 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?

Five required numeric parameters with no output schema place the burden on the description to explain what the tool returns (a classification? a discrepancy count?), and it does not. The conceptual vocabulary is present, but an agent cannot predict the result shape or how the five inputs combine.

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%, so every parameter is already documented in the schema. The description's English gloss ('matched requests, documented lockouts and unexplained starts') loosely maps to passende_starts, belegte_sperren and the residual starts_gesamt, but adds no format, unit, or reconciliation logic beyond what the schema says. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the domain objects (Thermostatanforderungen vs. gemessene Heizstarts) and the decision context (classifying an absent effect at the usage point), which is more than a restatement of the name. But it never states the actual operation — whether it computes a ratio, returns a verdict, or just echoes counts — and it does not differentiate itself from the many other _protokoll siblings. An agent can guess the topic but not the concrete output.

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 'bevor eine ausbleibende Wirkung am Nutzplatz eingeordnet wird' implies the trigger condition: use this before attributing a missing heating effect. That is real contextual guidance, but there is no when-not guidance and no named alternative among the numerous thermostat siblings. Usage is implied rather than prescribed.

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