Skip to main content
Glama

getecoback-raumklima

duschprotokoll_timer_trockenphasen_anteil

Read-only

Wasserlaufzeiten aus einer Duschzeituhr mit zwei belegten Trockenphasen rekonstruieren — Subtract verified water-off phases from an elapsed timer.

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": {
      "timer_s": "<timer_s>",
      "aus_a_ab": "<aus_a_ab>",
      "aus_a_bis": "<aus_a_bis>",
      "aus_b_ab": "<aus_b_ab>",
      "aus_b_bis": "<aus_b_bis>",
      "alle_stopps_erfasst": "<alle_stopps_erfasst>"
    },
    "name": "duschprotokoll_timer_trockenphasen_anteil"
  }
}

Input Schema

NameRequiredDescriptionDefault
timer_sYesGesamtdauer des gestarteten Timers.
aus_a_abYesBeginn der ersten vollständig wasserfreien Phase ab Timerstart.
aus_b_abYesBeginn der zweiten wasserfreien Phase.
aus_a_bisYesEnde der ersten Phase.
aus_b_bisYesEnde der zweiten Phase.
alle_stopps_erfasstYesSind sämtliche vollständig geschlossenen Phasen in diesen Zeiten enthalten?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 agent knows this is a pure computation with no side effects and no external data. The description reinforces this by framing the tool as subtraction/reconstruction. It does not disclose the failure behaviour when intervals overlap, exceed 'timer_s', or when 'alle_stopps_erfasst' is false, which is the main remaining behavioural unknown.

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 sentence, front-loaded with the reconstruction goal, with no filler or preamble. The German and English halves largely restate each other, which is mild redundancy rather than noise, so it stays efficient overall.

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 arithmetic tool with all parameters required, no output schema, and no stated return semantics. For a computation tool the agent needs to know the unit and shape of the result and the behaviour under inconsistent input, and the description supplies neither. The absence of an output schema shifts that burden onto the description, which does not carry it.

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 every parameter documented in German including ranges, so the schema carries the parameter burden. The description adds only the relational meaning that the two 'aus_*' pairs are dry phases to be subtracted, which is already implied by the schema wording. Baseline 3 applies.

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 concrete operation on concrete inputs — subtract two verified water-off phases ('aus_a', 'aus_b') from an elapsed timer to reconstruct water-on time. That is clearer than a restatement of the name. It stops short of differentiating from conceptually similar net-duration siblings such as lichterkette_timer_netto, and it never states what the reconstructed value actually is (a duration in seconds, a breakdown, or a validity verdict).

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?

'mit zwei belegten Trockenphasen' / 'verified water-off phases' implies a precondition: this tool only applies when exactly two fully closed dry phases are known. That is useful implied guidance. However, there is no explicit when-to-use versus alternatives, and no instruction on what to do when 'alle_stopps_erfasst' is false — the single most decision-relevant usage condition for this tool.

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