Skip to main content
Glama

getecoback-climate-weather

geraetegruppen_uebergabe_verbrauchsstelle_wechselbilanz

Read-only

Beim Wechsel eines gemessenen Geräts zwischen zwei Gruppenbilanzen eine ausstehende Zuordnung erkennen — Check the preserved total across a verified device reassignment between meters.

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": {
      "a_alt_wh": "<a_alt_wh>",
      "b_alt_wh": "<b_alt_wh>",
      "wechsel_wh": "<wechsel_wh>",
      "b_neuer_bericht_wh": "<b_neuer_bericht_wh>",
      "messgrenze_sauber": "<messgrenze_sauber>"
    },
    "name": "geraetegruppen_uebergabe_verbrauchsstelle_wechselbilanz"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_alt_whYesGespeicherte Energie der Ausgangsgruppe A für genau dieses Beobachtungsfenster.
b_alt_whYesGespeicherte Energie der empfangenden Gruppe B für dasselbe Beobachtungsfenster.
wechsel_whYesEnergie des nachweislich in A enthaltenen und künftig B zugeordneten Geräts in diesem Fenster.
messgrenze_sauberYesIst das Gerät vor der Korrektur nur A und keinem gemeinsam gezählten Oberzähler zugeordnet?
b_neuer_bericht_whYesTatsächlich neu berichteter Gruppentotalwert B für dasselbe Beobachtungsfenster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, closed-world check. The description adds that it detects a pending assignment and verifies a preserved total, but it does not explain the result format, failure conditions, or what qualifies as a valid reassignment beyond the input parameters.

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?

The definition is short and front-loads the operating scenario before the check itself. The German and English phrasing is somewhat duplicative and the em-dash structure is not perfectly crisp, but there is no unnecessary verbosity.

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?

The schema and annotations make invocation possible, but the tool has five required inputs and no output schema, so the description should do more to explain what a successful check returns or what an outstanding assignment means. It is adequate but leaves a clear gap around output 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%, and all five required parameters are documented directly in the schema. The description adds no additional parameter semantics, so the baseline of 3 is appropriate when the schema carries the full burden.

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 gives a specific check operation: detecting an outstanding assignment and preserving the total when a measured device is reassigned between two group balances. It is clear enough to distinguish this as a balance-check tool, though it does not explicitly differentiate itself from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the operative context clearly: use it during a device reassignment between two group balances and when checking a preserved total. It does not provide when-not guidance or name alternative tools, so it falls short of full usage guidance.

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