Skip to main content
Glama

getecoback-raumklima

betriebszustand_netzteil_grenze_wirkleistung

Read-only

Eine am Gerät erhobene Niedervolt-Angabe von gleichzeitig gemessener Netzaufnahme mit demselben Netzteil unterscheiden — Reconcile documented metering sides without treating output power as wall power.

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": {
      "eingang_w": "<eingang_w>",
      "ausgang_w": "<ausgang_w>",
      "fehlerband_w": "<fehlerband_w>",
      "selbes_netzteil_fenster": "<selbes_netzteil_fenster>"
    },
    "name": "betriebszustand_netzteil_grenze_wirkleistung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ausgang_wYesFür genau denselben stabilen Abschnitt passend dokumentierte Ausgangsleistung.
eingang_wYesBereits fachgerecht gemessene mittlere Wirkleistung der Netzseite für den stabilen Abschnitt.
fehlerband_wYesBelegter kombinierter absoluter Messspielraum.
selbes_netzteil_fensterYesGleiche Zeitfenster, Netzteil, Versorgungslast und keine gespeicherte Energie im Bilanzabschnitt schon bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 locality are covered and the description's job is to explain the reconciliation behavior itself. It does add the key semantic caveat that output power must not be equated with wall power, but it says nothing about how the error band (fehlerband_w) is applied, what conclusion is drawn when the sides fail to reconcile, or what the response contains — and there is no output schema to fall back on.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and the core distinction is front-loaded, so nothing is padded. However, it restates itself bilingually (German clause followed by an English gloss of the same idea), and the main German clause is elliptically compressed in a way that costs a reading rather than saving one.

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 four required parameters, no output schema and terse read-only annotations, the description needs to carry the comparison logic. It conveys what is being separated and the cardinal error to avoid, but leaves the decision rule around the tolerance band and the shape of the result unexplained — an agent knows the framing yet not what a call actually yields.

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 each of the four required parameters is documented in detail (measured mains real power, documented output power, combined absolute measurement tolerance, confirmation of same window/PSU/load/no stored energy). The description adds only the conceptual framing that the two watt values belong to different metering sides, which is consistent with but not richer than the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('unterscheiden' / 'Reconcile') and the resource (documented metering sides — device-side low-voltage reading vs. mains draw), and the English gloss 'without treating output power as wall power' pins the intent. But it never states what the tool actually produces from the two watt figures plus the error band (a verdict? a delta? a flag?), and it names no sibling to separate itself from near-identical neighbors such as betriebszustand_messwert_zwei_herstellerzeilen_trennen.

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 only implied: the same power supply and same stable window are presupposed ('mit demselben Netzteil'), and the 'without treating output power as wall power' clause hints at the misapplication to avoid. There is no explicit when-to-use statement, no exclusion, and no pointer to any alternative tool for the case where only one metering side is documented.

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