Skip to main content
Glama

getecoback-raumklima

duschdurchfluss_start_stopp_zeitfehler

Read-only

Einen protokollierten Eimertest mit Start- und Stoppungenauigkeit als Durchflussspanne lesen — Bound water flow with independently bounded endpoint timing error.

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": {
      "wasser_liter": "<wasser_liter>",
      "dauer_s": "<dauer_s>",
      "start_fehler_s": "<start_fehler_s>",
      "stopp_fehler_s": "<stopp_fehler_s>"
    },
    "name": "duschdurchfluss_start_stopp_zeitfehler"
  }
}

Input Schema

NameRequiredDescriptionDefault
dauer_sYesAbgelesene Versuchsdauer in Sekunden.
wasser_literYesAufgefangene gemessene Wassermenge in Litern.
start_fehler_sYesMaximale absolute Abweichung des Startpunkts in Sekunden.
stopp_fehler_sYesMaximale absolute Abweichung des Stopppunkts in Sekunden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 covered. The description adds genuine context beyond that by stating the result is a flow span (an interval) bounded by two independent endpoint errors, rather than a single flow value. It stops short of explaining how the bounds are combined or what units and limits apply to the computed span.

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?

The definition is short and front-loads the scenario, but it delivers the same content twice, once in German and once in English, and the English clause is a compressed restatement rather than added information. That bilingual redundancy costs space without adding guidance an agent can act on.

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?

With no output schema, the description carries the burden of describing the return value; it does indicate a flow span, but not the units, whether both interval bounds are returned or whether the span is inclusive. For a four-parameter computation tool with a non-obvious derived output, that leaves a meaningful gap an agent must resolve by calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the four parameters are fully documented with units, ranges, and meanings, giving a baseline of 3. The description goes one step beyond by clarifying that the start and stop errors are treated independently ("independently bounded endpoint timing error"), a semantic the schema does not state about how start_fehler_s and stopp_fehler_s relate.

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 resource (a logged bucket test, "Eimertest") and a specific outcome (a flow span, "Durchflussspanne") derived from bounded start/stop timing error, which distinguishes it from a plain flow measurement. It is slightly muddled by the verb "lesen" (read), since the tool evidently computes from four supplied measurements rather than retrieving a stored record, and it never names the sibling measuring tool it differs from.

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?

Usage is only implied: it applies when a bucket test has independent start and stop timing uncertainty. There is no explicit when-to-use or when-not, no prerequisites, and no pointer to the alternative sibling for a plain flow measurement, so an agent must infer the selection rule from the phrasing.

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