Skip to main content
Glama

getecoback-raumklima

stromgruppe_steuergeraet_weckvorgaenge_abgleich

Read-only

Gemessene Weckvorgänge und einzeln dokumentierte Befehle gegenüberstellen, wenn ein Aufwecken mehrere Befehle bedient — Audit which shared controller wakeups replaced repeated wake events.

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": {
      "befehle_a": "<befehle_a>",
      "befehle_b": "<befehle_b>",
      "ohne_wecken_allein": "<ohne_wecken_allein>",
      "weckvorgaenge": "<weckvorgaenge>",
      "weckenergie_wh": "<weckenergie_wh>"
    },
    "name": "stromgruppe_steuergeraet_weckvorgaenge_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
befehle_aYesZahl der protokollierten Anforderungen von Gerät A.
befehle_bYesZahl der protokollierten Anforderungen von Gerät B.
weckvorgaengeYesGemessene Weckvorgänge, jeweils ausgelöst durch mindestens eine der übrigen Anforderungen.
weckenergie_whYesGemessene Gesamtenergie der abgegrenzten Weckvorgänge.
ohne_wecken_alleinYesZahl einzeln protokollierter Anforderungen während bereits laufender Dauerphasen, ohne gemeinsamen Weckvorgang.

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 safety and locality are covered. The description adds that this is an audit/comparison of recorded measurements, but says nothing about what the comparison produces, whether the inputs must be consistent, or how mismatched counts are handled.

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 compact sentence with the operation front-loaded and the qualifying condition trailing; nothing is padded. The bilingual gloss is mildly redundant but aids disambiguation and costs little.

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 five-number, fully required, closed-world computation with no output schema, the description covers the inputs' relationship and the intent. The notable remaining gap is the shape of the result — whether it reports a replacement ratio, energy attribution, or a pass/fail audit verdict.

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% and each of the five numeric parameters carries its own German description, so the schema does the heavy lifting. The description adds no interpretation of the parameters beyond implying the A/B command counts and wake counts are being compared.

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 concrete operation — reconciling measured wake events against individually logged commands — and adds the triggering condition (one wakeup serving multiple commands). It is specific enough to distinguish this reconciliation from the other 'abgleich' siblings, though the German sentence is abstract and the English gloss mostly restates it.

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?

It gives one usage condition: 'wenn ein Aufwecken mehrere Befehle bedient'. There is no guidance on when not to use it, no prerequisites (e.g. that all five measurements must come from the same observation window), and no named alternative among the many sibling reconciliation tools.

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