Skip to main content
Glama

getecoback-raumklima

stromlogger_spitzenmittel_ausreisserabstand

Read-only

Ein protokolliertes Leistungsmaximum gegen einen passend aggregierten Mittelwert und bekannten Spitzenabschnitt prüfen — Test consistency of peak duration and aggregate energy.

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": {
      "fenster_s": "<fenster_s>",
      "mittel_w": "<mittel_w>",
      "spitze_mindestens_w": "<spitze_mindestens_w>",
      "spitzenabschnitt_s": "<spitzenabschnitt_s>",
      "gleicher_umfang": "<gleicher_umfang>"
    },
    "name": "stromlogger_spitzenmittel_ausreisserabstand"
  }
}

Input Schema

NameRequiredDescriptionDefault
mittel_wYesÜber die gesamte Dauer integriertes Zeitmittel in Watt.
fenster_sYesDauer des gesamten betrachteten Fensters in Sekunden.
gleicher_umfangYesSind beide Angaben für dieselbe Verbrauchsgrenze und Zeitbasis belegt?
spitzenabschnitt_sYesGemessene Dauer dieses Spitzenabschnitts innerhalb des Fensters.
spitze_mindestens_wYesBelegte Mindestlast über den gesamten Spitzenabschnitt in Watt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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. The description adds that this is a consistency test between peak duration and aggregate energy rather than a data fetch or mutation, which is genuinely useful framing. It stops short of saying what constitutes inconsistency, whether any thresholds are applied, or what happens to inputs that fail the check.

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?

Single sentence, front-loaded with the assessed entities, but the German and English halves largely restate each other rather than complementing one another, so half the text is redundant. The compound German noun in the name is never unpacked in either language.

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 five-required-parameter validation tool with no output schema, so the description carries the burden of explaining the return value and what a positive/negative consistency result looks like. It does neither, leaving the agent unable to predict whether the response is a boolean, a verdict report, or diagnostic values.

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 all five parameters (fenster_s, mittel_w, spitze_mindestens_w, spitzenabschnitt_s, gleicher_umfang) are already documented in the schema. The description adds no parameter-level meaning beyond referring loosely to "peak duration and aggregate energy"; baseline 3 applies when the schema does the work.

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 description names the operation ("prüfen") and the entities it relates (logged peak maximum, aggregated mean, known peak section), and the English clause narrows it to a duration/energy consistency test. But the phrasing is abstract enough that an agent cannot confidently tell this apart from sibling stromlogger checks such as kurzereignis_stichprobe or sequenz_counter_luecke; no sibling is named and the user-facing verb stays generic ("check").

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 call this versus other Stromlogger validation tools, no preconditions, and no exclusions. The agent must infer usage purely from the parameter names.

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