Skip to main content
Glama

getecoback-raumklima

strommessung_unterzaehler_netzbaum

Read-only

Doppelzählung einer Gerätegruppe unter einem gemeinsamen Zwischenzähler aus der Bilanz entfernen — Reconcile a nested submeter plus independent loads without counting its measured child twice.

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": {
      "gesamt_kwh": "<gesamt_kwh>",
      "gruppenzaehler_kwh": "<gruppenzaehler_kwh>",
      "teilgeraet_kwh": "<teilgeraet_kwh>",
      "gruppe_aussen_kwh": "<gruppe_aussen_kwh>",
      "gleicher_zeitraum": "<gleicher_zeitraum>"
    },
    "name": "strommessung_unterzaehler_netzbaum"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_kwhYesGesamter Haushalt im gemeinsamen Zeitraum in kWh.
teilgeraet_kwhYesGemessenes Teilgerät innerhalb der Gruppe.
gleicher_zeitraumYesAlle Werte decken denselben Zeitraum und dieselbe Flussrichtung ab?
gruppe_aussen_kwhYesUnabhängig außerhalb der Gruppe gemessene Verbraucher.
gruppenzaehler_kwhYesGemeinsamer Zwischenzähler für mehrere Geräte, inklusive Teilgerät.

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 a safe, read-only, closed-world operation. The description adds the important behavioral concept of avoiding double counting of a measured child, but it does not disclose the output format, calculation result, or any error conditions.

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 description is short and front-loads the purpose. The German-English repetition is somewhat redundant but still compact and easy to parse.

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 read-only calculation tool with five fully documented inputs and no output schema, the description explains the reconciliation concept but leaves the returned value and its interpretation unstated. It is adequate but has a clear completeness gap around output behavior.

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 coverage is 100%, and the schema already explains each parameter, including that the group meter includes the child device. The description reinforces the core relationship but does not add parameter-level meaning beyond what the schema provides.

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 states a specific reconciliation task: removing double counting for a device group under a shared submeter and handling nested plus independent loads. It is clear what the tool does, but it does not explicitly distinguish itself from the many other strommessung_* siblings.

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?

The description implies the scenario for use — a nested submeter with a measured child plus independent loads — but gives no explicit when-to-use guidance, exclusions, or alternatives among the sibling 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