Skip to main content
Glama

getecoback-raumklima

strommessung_raumzuordnung_ungeklaerter_anteil

Read-only

Bilanziere nach der Weitergabe eines Messgeräts zuordenbare und ungeklärte Energie — Separate allocated and unassigned energy from a shared power meter

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": {
      "zaehlerstart_kwh": "<zaehlerstart_kwh>",
      "zaehlerende_kwh": "<zaehlerende_kwh>",
      "raum_a_belegt_kwh": "<raum_a_belegt_kwh>",
      "raum_b_belegt_kwh": "<raum_b_belegt_kwh>",
      "belege_disjunkt": "<belege_disjunkt>"
    },
    "name": "strommessung_raumzuordnung_ungeklaerter_anteil"
  }
}

Input Schema

NameRequiredDescriptionDefault
belege_disjunktYesDie einzeln belegten Teilmessungen überschneiden sich nicht
zaehlerende_kwhYesEndwert desselben Zählers ohne Nullung
zaehlerstart_kwhYesStartwert am durchgehend geführten Zähler in kWh
raum_a_belegt_kwhYesNachweisbar in Raum A gemessene kWh
raum_b_belegt_kwhYesNachweisbar in Raum B gemessene kWh

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds nothing behavioral: it does not say what happens when belege_disjunkt is false or the partial readings overlap, nor whether continuity of zaehlerstart/zaehlerende is validated. For a reconciliation tool whose main failure mode is inconsistent inputs, that omission matters.

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?

A single compact sentence, front-loaded with the balancing action; the bilingual repetition is mildly redundant but helps disambiguate the German domain term. No filler or hedging.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a pure calculation tool with no output schema, so the description should indicate what comes back (allocated kWh per room vs. the unassigned residual). It does not, and it also omits the overlap preconditions, leaving the agent unable to anticipate either the result shape or error conditions.

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 five parameters including the disjunction flag are already documented in the schema. The description contributes only the framing that start/end values come from the same meter after handover, with no added detail on units, bounds, or the consequence of setting belege_disjunkt incorrectly. Baseline 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?

The description pairs a specific verb ("Bilanziere") with a precise resource: the split between energy assignable to rooms A/B and the unassigned remainder from one shared meter. That is enough for an agent to know what computation happens, though it never names a sibling (e.g. strommessung_a_b_messfehler or strommessung_va_w_einordnen) to delimit itself.

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 phrase "nach der Weitergabe eines Messgeräts" implies the situation that triggers the call — continuous readings on one meter after a handover — but there is no explicit when-to-use vs. when-not guidance and no alternative tool is mentioned. Usage must be inferred from the name and context.

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