Skip to main content
Glama

getecoback-raumklima

stromhistorie_strukturbruch_drei_fenster

Read-only

Einen beobachteten Stromverbrauchssprung zwischen drei geordneten Messfenstern von einer einmaligen Spitze unterscheiden — Screen a documented change against a following persistence check.

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": {
      "basis_kwh": "<basis_kwh>",
      "direkt_kwh": "<direkt_kwh>",
      "spaeter_kwh": "<spaeter_kwh>",
      "mindestabstand_kwh": "<mindestabstand_kwh>",
      "messaufgabe_gleich": "<messaufgabe_gleich>"
    },
    "name": "stromhistorie_strukturbruch_drei_fenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
basis_kwhYesVerbrauch im gleich langen Fenster vor dem bekannten Ereignis.
direkt_kwhYesVerbrauch im gleich langen ersten Fenster nach dem Ereignis.
spaeter_kwhYesVerbrauch im gleich langen zweiten Fenster nach dem Ereignis.
messaufgabe_gleichYesSind Messumfang und Haushaltsaufgabe vergleichbar geblieben?
mindestabstand_kwhYesEigener positiver Prüfspielraum für eine Abweichung.

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is known and the description need not restate it. The description adds that the comparison is purely arithmetic over three equal-length windows with a user-supplied minimum deviation threshold, which helps. It does not disclose what a call actually yields — a verdict, a classification, or a margin — and with no output schema that is a real gap.

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?

It is a single compact sentence, front-loaded with the decision being made, which is good. The German and English halves are largely duplicative rather than complementary ('from a one-time spike' vs 'persistence check'), so a slight redundancy keeps it off a 5.

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 five required parameters are documented in the schema and the tool is a side-effect-free calculation, so the essentials for invocation are present. Because there is no output schema, the description should say what the result looks like (e.g., 'persistent vs spike' verdict) and it does not, leaving the agent unsure how to consume the response.

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 parameter's German description already explains the window it represents and the >= 0.001 bound on mindestabstand_kwh. The description adds the concept of ordered windows but no format, unit, or normalization guidance beyond what the schema states, so the baseline of 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?

The description names a specific operation — distinguishing a consumption jump across three ordered measurement windows from a one-off spike — so the verb ('unterscheiden') and the resource (three ordered windows, basis/direkt/spaeter) are concrete. It is recognizable against the many other 'stromhistorie_*' siblings because of the three-window structural-break framing, but it never names an alternative tool explicitly.

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 'Screen a documented change against a following persistence check' implies the situation that calls for this tool: a known consumption change that must be confirmed as persistent rather than transient. There is no explicit when-not guidance and no pointer to a sibling for the simpler cases (e.g., single-window or day-shift comparisons in the sibling list), so the agent must infer scope.

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