Skip to main content
Glama

getecoback-climate-weather

warmwasser_erste_probe_dauer_ausschluss_unnotiert

Read-only

Eine protokollierte Warmwasserwartezeit mit nachträglich bekannt gewordener Timer-Vorlaufzeit korrigieren — Restore elapsed run-up from deliberate or accidental timer lead.

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": {
      "timerstart": "<timerstart>",
      "oeffnen_fruehestens": "<oeffnen_fruehestens>",
      "oeffnen_spaetestens": "<oeffnen_spaetestens>",
      "ziel": "<ziel>",
      "gleiche_aufzeichnung": "<gleiche_aufzeichnung>"
    },
    "name": "warmwasser_erste_probe_dauer_ausschluss_unnotiert"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielYesDokumentierter Zeitpunkt, an dem der gewählte Zustand erstmals beobachtet wurde.
timerstartYesTimerstart auf einer gemeinsamen Sekundenskala.
oeffnen_fruehestensYesFrühester anhand der Aufzeichnung erkennbarer Moment des Öffnens.
oeffnen_spaetestensYesSpätester anhand der Aufzeichnung erkennbarer Moment.
gleiche_aufzeichnungYesStammen alle vier Zeitpunkte aus derselben durchgehenden Aufzeichnung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety is covered. The description adds the key behaviour that this is a retrospective correction/restoration of an elapsed run-up rather than a fresh measurement, but 'korrigieren' could be read as mutating a stored log, and the description does not clarify that it only returns a corrected value. No return shape or failure conditions are described.

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?

A single front-loaded sentence with the correction target stated before the qualifier. The bilingual German/English pairing is mildly redundant, but the English clause adds the deliberate-versus-accidental distinction rather than merely translating.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a fully parameterized computation with five required, homogeneous, well-described numeric inputs and no output schema, so the description does not need to document return values. Combined with 100% schema coverage it supplies enough framing for correct invocation.

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 five time points is already documented in the schema and the baseline of 3 applies. The description adds conceptual framing — the timer lead time versus the observed opening window and the deliberate/accidental origin of the lead — but no ordering constraints or units beyond what the schema states.

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 and resource: correct a logged hot-water waiting time when a timer lead time became known afterwards. That is far more than a restatement of the name, though it never contrasts itself with near-neighbours such as warmwasser_warteverlust or warmwasser_wartezeit_zapfstellen, so sibling differentiation is left to inference.

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 triggering situation is implied ('nachträglich bekannt gewordener Timer-Vorlaufzeit' — the lead time was discovered after the fact), which tells an agent roughly when the tool applies. It gives no explicit when-not conditions, no prerequisites such as data consistency requirements, and no named alternatives.

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