Skip to main content
Glama

getecoback-climate-weather

stromverlauf_freie_und_belegte_stunden

Read-only

Mehrverbrauch einer teilweise belegten Phase aus separat belegten Ruhe- und Nutzungsstunden herauslesen — Assess the energy associated with occupied hours without treating every calendar hour as use.

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": {
      "phase_stunden": "<phase_stunden>",
      "belegte_stunden": "<belegte_stunden>",
      "phase_wh": "<phase_wh>",
      "ruhe_wh_stunde": "<ruhe_wh_stunde>"
    },
    "name": "stromverlauf_freie_und_belegte_stunden"
  }
}

Input Schema

NameRequiredDescriptionDefault
phase_whYesGemessene Gesamtenergie des späteren Fensters in Wh.
phase_stundenYesGemessene Dauer des gesamten späteren Fensters in Stunden.
ruhe_wh_stundeYesIn einer separat gemessenen, vergleichbaren Ruhephase ermittelte Wh je Stunde.
belegte_stundenYesDokumentierte tatsächlich belegte Stunden innerhalb des Fensters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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. The description adds the conceptual behavior (excess consumption is isolated using a separately measured rest baseline), which goes slightly beyond the annotations, but says nothing about whether the result is a derived value, how negative outcomes are treated, or about precision/limits.

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?

Short and front-loaded on the action, but the German sentence and the English gloss largely restate each other rather than contributing distinct information. The dense German compound phrasing also takes effort to parse for little extra precision.

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 four-required-parameter computation with no output schema, so the description carries the burden of explaining what comes back (presumably an excess-energy figure in Wh) and it does not. The relationship between phase_stunden and belegte_stunden, central to interpreting the tool, is left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, and the description does add genuine meaning by framing ruhe_wh_stunde as a baseline from a comparable rest phase and belegte_stunden as the documented occupancy within the window. It stops short of stating the computation, which the agent must infer from the parameter names.

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 concrete computation: derive the excess consumption ('Mehrverbrauch') of a partially occupied phase from separately measured rest and usage hours. An agent can tell it is an energy-attribution/estimation tool rather than a plain meter reader, though the description never names or contrasts any sibling such as stromverlauf_planband_vs_messband.

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 'without treating every calendar hour as use' implies the use case — partial occupancy where a naive hours-times-rate calculation would be wrong — but this is only implied. There is no explicit when-to-use/when-not statement, no prerequisites (e.g. that ruhe_wh_stunde must come from a comparable rest phase), and no named alternative.

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