Skip to main content
Glama

getecoback-climate-weather

warmwasser_nutzfenster_profil_unterbrechung

Read-only

Bei gemessenem Warmwasserprofil nutzbare zusammenhängende Phasen von einer Unterbrechung trennen — Check continuous usability across a recorded temperature interruption.

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": {
      "erster_beginn": "<erster_beginn>",
      "erstes_ende": "<erstes_ende>",
      "zweiter_beginn": "<zweiter_beginn>",
      "zweites_ende": "<zweites_ende>",
      "mindestdauer": "<mindestdauer>",
      "vermerk_durchgaengig": "<vermerk_durchgaengig>"
    },
    "name": "warmwasser_nutzfenster_profil_unterbrechung"
  }
}

Input Schema

NameRequiredDescriptionDefault
erstes_endeYesEnde der ersten lückenlos beobachteten Phase im Wunschbereich.
mindestdauerYesSelbst gewählte notwendige Dauer eines zusammenhängenden Abschnitts.
zweites_endeYesEnde der zweiten lückenlos beobachteten Phase.
erster_beginnYesErstes Erreichen des Wunschbereichs ab Start.
zweiter_beginnYesErneutes Erreichen des Bereichs.
vermerk_durchgaengigYesWurden beide durchgängigen Abschnitte statt nur Einzelwerte beobachtet?

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 the safety profile is covered, but the description adds almost no behavioral context beyond that: it does not say what the tool returns (a verdict, a trimmed interval, a boolean), how 'nutzbar' is decided relative to mindestdauer, or what happens when the interruption invalidates the window. For a multi-parameter evaluation tool with no output schema, this leaves the agent guessing about the result.

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-loads the subject, but the single sentence is split across two languages and restates itself rather than building information. There is no wasted padding, but also no structure that helps an agent parse the operation.

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?

With six required numeric/boolean parameters, no output schema, and a non-obvious domain concept, the description should clarify the decision being computed and the shape of the result. It does not, so an agent can supply the parameters but cannot predict or verify what comes back.

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 each of the six parameters is already documented in the schema, which sets the baseline at 3. The description mentions the profile and the interruption conceptually but adds no meaning about how the two phases, mindestdauer, and vermerk_durchgaengig interact.

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 a specific operation (separating usable contiguous phases around an interruption in a recorded hot water profile), so the domain is identifiable. However, it is an abstract check whose output is never characterized, and the bilingual split sentence ('...trennen — Check continuous usability...') makes the actual operation harder to pin down than a single clear statement would. Siblings such as warmwasser_erholung_zwei_gepruefte_pausen are equally cryptic, so no 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, when not to, or which sibling to prefer for a related hot-water assessment. The only implicit context is 'bei gemessenem Warmwasserprofil', which is a data precondition rather than usage guidance.

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