Skip to main content
Glama

getecoback-climate-weather

stromimpuls_export_ereignisabgleich

Read-only

Die Zahl erfasster Zählerimpulse mit einer unabhängigen Energiespanne und unbekannter Randphase abgleichen — Cross-check recorded pulse counts against a documented energy-per-pulse scale.

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": {
      "energie_unter_wh": "<energie_unter_wh>",
      "energie_ober_wh": "<energie_ober_wh>",
      "wh_je_impuls": "<wh_je_impuls>",
      "erfasst_impulse": "<erfasst_impulse>",
      "gleiche_grenzen": "<gleiche_grenzen>"
    },
    "name": "stromimpuls_export_ereignisabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
wh_je_impulsYesDokumentierte Wh pro Verbrauchsimpuls für genau dieses Register.
energie_ober_whYesBelegte obere Energiegrenze im vollständigen Zeitfenster, in Wh.
erfasst_impulseYesTatsächlich exportierte Impulse im selben Zeitfenster.
gleiche_grenzenYesSind Zeitgrenzen und Verbrauchsregister beider Messquellen belegt?
energie_unter_whYesBelegte untere Energiegrenze im vollständigen Zeitfenster, in Wh.

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 safety and scope are covered by structured data. The description adds that the comparison is against a documented scale and that the phase boundary is unknown, which is useful framing beyond the annotations. However it never states what the cross-check produces (a match verdict, a deviation, a tolerance decision) or how conflicting inputs 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?

It is a single, front-loaded sentence with the action and the two operands stated first. The bilingual restatement (German then English) duplicates the same content, which is mildly wasteful but short enough not to obscure the definition.

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?

With five required numeric/boolean parameters and no output schema, the definition must carry the meaning of the result, and it does not say what a successful or failing cross-check looks like or what the agent should do with a mismatch. The read-only annotation and complete schema descriptions cover most of the remaining burden, so the definition is adequate but has a clear gap around outcome interpretation.

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 every parameter including bounds and units is already documented in the schema; baseline 3 applies. The description reinforces the pairing of 'erfasste Impulse' with 'Wh je Impuls' and the energy span, but adds no semantics beyond that and leaves 'gleiche_grenzen' (whether both sources' time windows and register are evidenced) unexplained.

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 specific action (abgleichen / cross-check) and two concrete resources: recorded pulse counts and a documented energy-per-pulse scale. It also flags the two distinguishing conditions of the scenario (independent energy span, unknown phase), so an agent can tell this is a plausibility cross-check rather than a plain export. It does not explicitly contrast with any sibling, which keeps it below 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?

There is no explicit when-to-use or when-not-to-use statement, no prerequisites, and no named alternative among the many siblings. The phrases 'unabhängige Energiespanne' and 'unbekannte Randphase' hint at the situation the tool is meant for, but the agent must infer the trigger conditions itself.

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