Skip to main content
Glama

getecoback-climate-weather

haushaltsstrom_messlauf_vor_lastwechsel_fenster

Read-only

Ein geplantes Haushalts-Messfenster durch erwartete kurzzeitige Zusatznutzungen prüfen und den zuerst neu abzusprechenden Abschnitt finden — Identify which scheduled background-load changes compromise a shared baseline observation.

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": {
      "grundprobe_ab_min": "<grundprobe_ab_min>",
      "grundprobe_bis_min": "<grundprobe_bis_min>",
      "a_zusatz_ab_min": "<a_zusatz_ab_min>",
      "a_zusatz_bis_min": "<a_zusatz_bis_min>",
      "b_zusatz_ab_min": "<b_zusatz_ab_min>",
      "b_zusatz_bis_min": "<b_zusatz_bis_min>"
    },
    "name": "haushaltsstrom_messlauf_vor_lastwechsel_fenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_zusatz_ab_minYesBestätigter Beginn einer zusätzlichen Nutzung aus Zimmer A.
b_zusatz_ab_minYesBestätigter Beginn einer anderen zusätzlichen Nutzung aus Zimmer B.
a_zusatz_bis_minYesBestätigtes Ende desselben Zusatzfensters.
b_zusatz_bis_minYesBestätigtes Ende desselben Zusatzfensters.
grundprobe_ab_minYesStart des vereinbarten ununterbrochenen Beobachtungsfensters.
grundprobe_bis_minYesEnde derselben Probe.

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 known and the bar is lower. The description adds that this is a conflict-detection/ordering computation over a baseline window, which is useful, but it never says how a conflict is determined, what 'zuerst neu abzusprechen' is ranked by, or what the result looks like.

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?

Two sentences are front-loaded with the action, but the English sentence largely restates the German one rather than adding information, so half the text is near-duplicate. The lead clause is dense and heavily compounded, slowing parsing.

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 six-parameter, all-required computational tool with no output schema, so the description must explain the result and the conflict/reordering logic — and it does not. Nothing tells the agent how overlaps between grundprobe and a/b windows are resolved, what tie-breaking produces the 'zuerst' section, or whether an empty result is possible.

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 all six minute-offset parameters individually documented including their 0–1440 bounds, so the schema carries the parameter burden. The description only loosely maps its 'Zusatznutzungen aus Zimmer A/B' and 'shared baseline' language onto those fields without adding format or constraint detail, so baseline 3 applies.

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 German half names a concrete action (prüfen eines geplanten Messfensters gegen erwartete Zusatznutzungen) plus a deliverable (den zuerst neu abzusprechenden Abschnitt finden), so the resource and operation are identifiable. However, it never distinguishes itself from the many similarly named window tools (e.g. haushaltsstrom_vereinbarte_spitzenbeobachtung, haushaltsstrom_geteilte_nutzung_szenario), and the abstract phrasing leaves the exact operation ambiguous.

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 explicit statement of when this tool should be used instead of the sibling household-measurement tools, and no exclusions or preconditions. At best, 'geplantes ... Messfenster prüfen' implies a pre-scheduling validation step, which the agent must infer.

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