Skip to main content
Glama

getecoback-raumklima

stromgruppe_unbeobachtete_gemeinsamlast_erkennung

Read-only

Aus einem dokumentierten Zeitsaldo prüfen, ob unerwarteter Verbrauch sicher außerhalb beider bekannten Betriebsfenster vorkommt — Detect unexplained energy in recorded both-idle periods.

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": {
      "beide_ruhig_wh": "<beide_ruhig_wh>",
      "beide_ruhig_min": "<beide_ruhig_min>",
      "gruppenruhe_max_w": "<gruppenruhe_max_w>",
      "ruhe_belegt": "<ruhe_belegt>"
    },
    "name": "stromgruppe_unbeobachtete_gemeinsamlast_erkennung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruhe_belegtYesSind Betriebszustände und Messumfang für diese Zeiten unabhängig bestätigt?
beide_ruhig_whYesGemessene Energie in vollständig dokumentierten Phasen ohne aktive Nutzung beider Geräte.
beide_ruhig_minYesGesamtdauer dieser überschneidungsfreien Phasen.
gruppenruhe_max_wYesVergleichbar gemessene oder belegte gemeinsame obere Ruhestromrate mit allen bekannten Geräten.

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a meaningful behavioral constraint — the result is only meaningful when the idle periods lie securely outside both known operating windows — but says nothing about what the check returns (flag? residual quantity?) or how 'sicher' is decided.

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?

Two compact clauses with the core condition front-loaded, followed by a short English gloss. The bilingual duplication is mildly redundant but useful for matching vocabulary; no filler sentences.

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?

For a four-parameter read-only analysis tool with no output schema, the description covers the input precondition but not the result: an agent cannot tell whether it receives a boolean, a residual consumption figure, or an error when documentation is insufficient. That return-shape gap is the main missing piece.

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 four parameters (beide_ruhig_wh, beide_ruhig_min, gruppenruhe_max_w, ruhe_belegt) are already explained in the schema. The description adds no per-parameter meaning, such as how gruppenruhe_max_w is used as a threshold or why ruhe_belegt gates the check; 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 description names a concrete verb (prüfen/detect) and a concrete target (unerwarteter Verbrauch / unexplained energy) and scopes it to energy falling 'sicher außerhalb beider bekannten Betriebsfenster', which is more specific than the bare tool name. It is distinguishable from measurement-splitting siblings, though it never contrasts itself with any of them explicitly.

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 only implied: the phrase 'Aus einem dokumentierten Zeitsaldo' and the annotation openWorldHint=false signal that this applies to recorded, confirmed idle-period data rather than live or open-ended data. There is no explicit statement of when to pick this over the sibling detection tools (e.g. gegenlaeufige_lastwechsel_netto or vier_betriebszustaende_wechselwirkung), and no exclusions.

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