Skip to main content
Glama

getecoback-raumklima

stromgruppe_geraeteband_aus_gesamtmessung

Read-only

Den möglichen Verbrauch eines Geräts aus einer Gesamtmessung und belegten Bandbreiten der anderen Lasten eingrenzen — Bound one device from aggregate energy and independently justified remaining-load ranges.

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_wh": "<gesamt_wh>",
      "andere_min_wh": "<andere_min_wh>",
      "andere_max_wh": "<andere_max_wh>",
      "gemeinsamer_messumfang": "<gemeinsamer_messumfang>"
    },
    "name": "stromgruppe_geraeteband_aus_gesamtmessung"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_whYesGemessene Energie aller bestätigten Lasten im selben Fenster.
andere_max_whYesBelegte obere Grenze für diese übrigen Lasten.
andere_min_whYesBelegte untere Grenze für alle übrigen Lasten zusammen.
gemeinsamer_messumfangYesSind Zählerumfang und die Grenzen für sämtliche übrigen Lasten bestätigt?

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add computation behavior. It does not state what happens when the bounds are inconsistent with the total (e.g. an empty or negative band) nor how the boolean confirmation gate changes the result. Useful framing, but the edge-case behavior a caller would want is absent.

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 tight sentence in each language, with the operative concept (bounding one device from a total minus justified ranges) front-loaded before the qualifier. The bilingual duplication is deliberate for a German-language toolset rather than padding, though it adds no new information.

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?

All four required parameters are documented and the tool is a pure read-only computation, so nothing critical is missing for invocation. However, with no output schema, the description never indicates what the result looks like — presumably a feasible consumption interval — leaving the agent to guess the return shape and its behavior under infeasible inputs.

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 the schema already explains all four parameters, including the three energy bounds and the confirmation flag. The description only restates them collectively as 'belegte Bandbreiten der anderen Lasten' and adds no syntax, units, or interaction detail beyond that. Baseline 3 applies.

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?

States a specific verb and resource: 'Den möglichen Verbrauch eines Geräts ... eingrenzen' / 'Bound one device from aggregate energy and independently justified remaining-load ranges.' The agent knows this computes an interval for a single device rather than detecting unattributed load or netting counter-flows like the sibling stromgruppe_* tools. It lacks an explicit contrast naming when this is the right sibling versus, say, the unbeobachtete Gemeinsamlast detection, so it stops short of a 5.

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 implied by the phrasing 'aus einer Gesamtmessung und belegten Bandbreiten der anderen Lasten' – it applies when an aggregate reading exists alongside independently justified bounds. There is no explicit statement of prerequisites, no when-not condition, and no named alternative for the case where only the aggregate is known.

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