Skip to main content
Glama

getecoback-climate-weather

warmwasser_wartezeit_zapfstellen

Read-only

Unabhängige Anlaufzeiten zweier Warmwasser-Zapfstellen einordnen — Compare waiting times at two taps measured from independent cold starts.

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": {
      "zeit_a_s": "<zeit_a_s>",
      "zeit_b_s": "<zeit_b_s>",
      "unabhaengig": "<unabhaengig>",
      "gleiche_entnahme": "<gleiche_entnahme>"
    },
    "name": "warmwasser_wartezeit_zapfstellen"
  }
}

Input Schema

NameRequiredDescriptionDefault
zeit_a_sYesSekunden bis zur gleichen beobachteten Zieltemperatur an Stelle A.
zeit_b_sYesSekunden bis zur gleichen beobachteten Zieltemperatur an Stelle B.
unabhaengigYesBeide Messungen begannen nach vergleichbarer Abkühlung ohne vorgewärmte gemeinsame Leitung?
gleiche_entnahmeYesEntnahmerate und Zieltemperatur der Messungen entsprechen sich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety is covered. Beyond that the description adds nothing: it does not say what the tool returns (a verdict, a delta, a rating) or what happens when unabhaengig or gleiche_entnahme is false — whether it refuses, warns, or still compares.

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?

Two short bilingual sentences with the core comparison front-loaded and no filler. The German and English halves are near-duplicates, which costs a little space but keeps the definition readable.

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?

There is no output schema, so the description carries the burden of explaining the return value, and it does not — an agent cannot tell whether it receives a comparison, a boolean, or a classification. The handling of the two guard booleans is likewise unexplained.

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 the schema already explains all four parameters including units, bounds, and the meaning of the two booleans. The description only echoes the 'independent cold starts' idea already carried by unabhaengig, adding no new meaning.

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 English half names a concrete verb and resource: compare waiting times at two taps from independent cold starts. The German 'einordnen' (assess/classify) is vaguer than 'compare', and the description never states what the assessment produces, so it stops short of a 5.

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 'independent cold starts' framing implies the measurement precondition, but there is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as warmwasser_warteverlust or warmwasser_aufheizzeit_ideal. Usage has to be inferred from the scenario wording.

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