Skip to main content
Glama

getecoback-climate-weather

stromspitze_zwei_lasten_einzelursache_pruefen

Read-only

Ein Gruppenmaximum gegen belegte Einzel- und Hintergrundobergrenzen auf mögliche Überlagerung prüfen — Rule out a lone active load only when all relevant peak ceilings are documented.

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": {
      "gruppenmaximum_w": "<gruppenmaximum_w>",
      "a_max_w": "<a_max_w>",
      "b_max_w": "<b_max_w>",
      "rest_max_w": "<rest_max_w>",
      "grenzen_belegt": "<grenzen_belegt>"
    },
    "name": "stromspitze_zwei_lasten_einzelursache_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_max_wYesBelegte Obergrenze von Gerät A allein.
b_max_wYesBelegte Obergrenze von Gerät B allein.
rest_max_wYesBelegte Obergrenze des ganzen übrigen Verbrauchs, einschließlich Ruhestrom.
grenzen_belegtYesSind alle drei Grenzen im betrachteten Zeitraum und Messraster nachvollziehbar?
gruppenmaximum_wYesAuf demselben Zeitmaß gemessenes mittleres Gruppenmaximum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that: the check's verdict depends on documentation completeness, so an undocumented ceiling limits the conclusion. It does not state the exact verdict shape, which leaves a small 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?

Two front-loaded sentences with no filler; the German statement comes first and the English gloss refines it. The German and English halves are not perfectly parallel (checking for superposition vs. ruling out a lone load), which costs a little precision but no length.

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?

Five required parameters with no output schema mean the description should say what a positive/negative result looks like, and it never does — an agent knows the decision rule but not the return value. What is present (precondition, decision logic) is accurate and adequate for calling the tool.

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 coverage is 100% and every parameter is described in the schema (Gerät A, Gerät B, Rest, Gruppenmaximum, grenzen_belegt). The description contributes the conceptual relation — group maximum versus the sum of documented individual and background ceilings — but adds no format, unit, or measurement-grid guidance beyond that relation. Baseline 3 applies 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 description names a specific verb+resource: checking a group maximum against documented individual and background ceilings for possible superposition ('Überlagerung'). An agent can tell this is a peak-attribution consistency check, though it never names a sibling or scope boundary (e.g. how it differs from strompaket_auslastung_pruefen).

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 second clause gives a real decision rule — a lone active load may only be ruled out when all relevant peak ceilings are documented — which implies the precondition carried by grenzen_belegt. However, there is no explicit when-to-use/when-not framing against any alternative tool, so the guidance is implied rather than stated.

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