Skip to main content
Glama

getecoback-raumklima

stromzaehler_sprung_leistungsplausibilitaet

Read-only

Sprung zwischen zwei bestätigten Stromzählerständen gegen eine dokumentierte obere Wirkleistung prüfen — Flag a cumulative-meter jump beyond the supported energy bound.

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": {
      "zaehler_sprung_wh": "<zaehler_sprung_wh>",
      "dauer_s": "<dauer_s>",
      "maximale_wirkleistung_w": "<maximale_wirkleistung_w>",
      "ablesespielraum_wh": "<ablesespielraum_wh>",
      "gleiche_skala_belegt": "<gleiche_skala_belegt>"
    },
    "name": "stromzaehler_sprung_leistungsplausibilitaet"
  }
}

Input Schema

NameRequiredDescriptionDefault
dauer_sYesBelegte verstrichene Zeit zwischen den Ablesungen in Sekunden.
zaehler_sprung_whYesAnstieg des kumulierten Verbrauchszählers in Wh.
ablesespielraum_whYesMaximaler kombinierter Spielraum beider Ablesungen in Wh.
gleiche_skala_belegtYesSind Gerät, Register, Einheiten und Ablesepunkte bestätigt?
maximale_wirkleistung_wYesDokumentierte obere Wirkleistung genau am gemessenen Anschluss in Watt.

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 state readOnlyHint=true and openWorldHint=false. The description adds that it compares against a documented upper active power and flags a jump beyond the supported energy bound, but it does not describe the result format, boundary semantics, or edge-case handling.

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?

A single front-loaded sentence with no wasted wording; the bilingual restatement is compact and reinforces the same precise purpose.

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 five-parameter validation tool with no output schema, the description communicates intent but is thin on what a flag looks like and how boundary values are treated. The rich input schema compensates for missing parameter detail.

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 all five required parameters are documented in the schema itself. The description adds no parameter-level meaning 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?

Names a specific verb (prüfen/flag), resource (Sprung zwischen zwei bestätigten Stromzählerständen), and condition (gegen eine dokumentierte obere Wirkleistung). It is clear what validation is performed, though it does not explicitly differentiate itself from sibling meter-checking tools.

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 implied: use this when a jump between confirmed meter readings must be checked against a documented maximum active power. There is no explicit when-not guidance or mention of alternatives such as stromzaehler_impulsleistung or doppelregister_abgleichen.

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