Skip to main content
Glama

getecoback-climate-weather

stromausfall_nachlauf_und_ruhe

Read-only

Stromaufnahme nach einer dokumentierten Unterbrechung vom vorherigen Ruhen und einem Folgetag abgrenzen — Compare a measured restart block against a separate same-duration idle baseline.

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": {
      "block_min": "<block_min>",
      "nach_wiederkehr_wh": "<nach_wiederkehr_wh>",
      "normalruhe_wh": "<normalruhe_wh>",
      "folgetag_wh": "<folgetag_wh>",
      "gleiche_verbraucher": "<gleiche_verbraucher>"
    },
    "name": "stromausfall_nachlauf_und_ruhe"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_minYesLänge beider tatsächlich beobachteter Vergleichsfenster.
folgetag_whYesVerbrauch eines dritten gleich langen Fensters am Folgetag, in Wh.
normalruhe_whYesVerbrauch eines Fensters gleicher Länge ohne Unterbrechung und ohne übliche aktive Nutzung, in Wh.
nach_wiederkehr_whYesVerbrauch nach Stromwiederkehr in Wh.
gleiche_verbraucherYesSind Zählerumfang und übliche Lasten in allen Fenstern tatsächlich vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 safety is covered, but the description adds little beyond that. It never says what the comparison produces (absolute delta, ratio, per-window attribution) despite there being no output schema, and it does not explain that gleiche_verbraucher acts as a comparability gate that presumably blocks or qualifies the result. For a pure computation tool with no return-value documentation, this is a meaningful gap.

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?

It is short and front-loaded, but the second clause largely restates the first in another language instead of adding information, and the German phrasing is dense. Space that could have explained the three-window comparison or the boolean gate is spent on redundancy.

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?

Five required parameters, a domain-specific comparison, no output schema, and no explanation of return values or of the gleiche_verbraucher precondition. The description is not sufficient on its own for an agent to call this correctly with confidence.

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 baseline is 3. The description reinforces the notion of equal-length observation windows ('same-duration'), which matches block_min, but it says nothing about the third window (folgetag_wh) or the boolean comparability flag, so it does not extend meaning beyond the schema.

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 English half states a recognizable operation — comparing a measured restart consumption block against a same-duration idle baseline — but the German half is opaque ('vom vorherigen Ruhen und einem Folgetag abgrenzen'), and the two halves do not fully agree. The schema contains three observed windows (nach_wiederkehr_wh, normalruhe_wh, folgetag_wh) while the description names only two, so an agent cannot fully pin down the comparison from the text. No sibling differentiation is offered.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus alternatives, no prerequisites (e.g. that an interruption must be documented), and no exclusion of nearby tools such as stromverlauf_freie_und_belegte_stunden or nachtluft_waerme_und_wasser_energievergleich. The agent must infer the trigger condition from the name alone.

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