Skip to main content
Glama

getecoback-climate-weather

dusche_temperatur_streuung

Read-only

Schwankung aus drei gemessenen Warmwassertemperaturen während eines gleich eingestellten Duschtests auswerten — Summarize observed tap-temperature stability from three readings.

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": {
      "start_c": "<start_c>",
      "mitte_c": "<mitte_c>",
      "ende_c": "<ende_c>",
      "fehler_je_c": "<fehler_je_c>",
      "ohne_aenderung": "<ohne_aenderung>"
    },
    "name": "dusche_temperatur_streuung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_cYesLetzter Messwert in °C.
mitte_cYesMittlerer Messwert in °C.
start_cYesErster Messwert nach der anfänglichen Wartezeit in °C.
fehler_je_cYesAbsoluter Fehler pro Messung in °C.
ohne_aenderungYesArmaturenstellung, Durchfluss und Messort gleich gehalten?

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 externally; the description adds that the operation is an evaluation of three prior readings under constant conditions. It does not say what the 'summary' consists of (spread, max deviation, verdict), and with no output schema that leaves a real gap in behavior disclosure.

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?

The German sentence is front-loaded and precise, and the English restatement aids disambiguation. The bilingual duplication is mildly redundant but short enough not to burden the reader.

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?

For a small read-only computation tool with full schema coverage, the definition is adequate but not complete: with no output schema, the agent is not told what a 'stability summary' returns or how the error tolerance (fehler_je_c) affects the verdict, which is central to interpreting the result.

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 all five parameters are already documented, and the description adds no meaning beyond them. It only maps loosely to 'three readings' (start/mitte/ende) and says nothing about fehler_je_c or the ohne_aenderung guard.

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 ('auswerten'/'summarize') and a specific resource ('Schwankung aus drei gemessenen Warmwassertemperaturen' / tap-temperature stability from three readings), which is clearly distinct from sibling tools like duschdurchfluss_messen or dusche_waermeleistungsbedarf. It does not, however, explicitly contrast itself with those siblings.

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 phrase 'während eines gleich eingestellten Duschtests' implies the precondition under which the tool applies (three readings taken under identical settings), which is reinforced by the ohne_aenderung parameter. There is no explicit when-to-use/when-not guidance or named alternative for a different measurement scenario.

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