Skip to main content
Glama

getecoback-climate-weather

stromverbrauch_lastfenster_audit

Read-only

Drei gemessene, unterschiedlich lange Lastfenster anhand der mittleren Leistung einordnen. — Identify the highest average-demand window without confusing a long window with a high peak.

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": {
      "a_kwh": "<a_kwh>",
      "a_min": "<a_min>",
      "b_kwh": "<b_kwh>",
      "b_min": "<b_min>",
      "c_kwh": "<c_kwh>",
      "c_min": "<c_min>"
    },
    "name": "stromverbrauch_lastfenster_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesGemessene Energie in Fenster A in kWh.
a_minYesDauer Fenster A in Minuten.
b_kwhYesGemessene Energie in Fenster B in kWh.
b_minYesDauer Fenster B in Minuten.
c_kwhYesGemessene Energie in Fenster C in kWh.
c_minYesDauer Fenster C in Minuten.

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 by structured data. The description contributes one genuine behavioral fact beyond that: the ranking basis is mean power (energy normalized by duration), not raw energy, which matters for windows of unequal length. It says nothing about what the response looks like (labels, ranking shape, per-window averages), which is a meaningful omission for a pure-computation tool.

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?

Two short sentences, front-loaded with the operation, with the interpretive caveat second. The German sentence and the English gloss overlap considerably, but the English line does add the specific goal ('highest average-demand window') and the failure mode to avoid, so the redundancy earns some of its space.

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?

There is no output schema, so the description is the only place the response shape could be described, and it is not: the agent cannot tell whether it receives a winning window label, a ranked list, or computed averages. For a six-required-parameter, fully deterministic calculation tool, that leaves a real gap even though the input side is fully documented.

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%, with every parameter already carrying unit and range documentation (kWh, minutes, bounds). The description adds only the framing that the three windows differ in length and that the comparison is by mean power, which hints at the energy/duration division without spelling it out. Baseline 3 is appropriate when the schema does the heavy lifting.

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 English gloss states a specific outcome: identify the highest average-demand window among three differently sized measurement windows, and explicitly warns against the long-window/high-peak confusion. That is more than a restatement of the name. It stops short of 5 because it never names or distinguishes any sibling tool, so the agent must infer the boundary on its own.

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 tool applies when you have three measured energy+duration pairs of unequal length to rank. The caution 'without confusing a long window with a high peak' implicitly tells the agent when this tool is the right one rather than a naive total-consumption comparison. There is no explicit when-not condition and no named alternative, so it stays at minimum-viable guidance.

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