Skip to main content
Glama

getecoback-climate-weather

sparbrause_mindestdurchfluss

Read-only

Gemessenen Duschdurchfluss gegen den dokumentierten Einschaltwert des Durchlauferhitzers prüfen — Compare measured shower flow with the heater’s specified activation threshold.

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": {
      "documented_min_l_min": "<documented_min_l_min>",
      "observed_l_min": "<observed_l_min>"
    },
    "name": "sparbrause_mindestdurchfluss"
  }
}

Input Schema

NameRequiredDescriptionDefault
observed_l_minYesGemessener Durchfluss bei üblicher Einstellung in l/min.
documented_min_l_minYesDurch Herstellerunterlagen belegter Mindestdurchfluss in l/min. 0 steht für unbekannt.

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?

readOnlyHint and openWorldHint are already declared, so the safety profile is covered. The description adds that this is a pure comparison against a documented threshold, but says nothing about the verdict produced, tolerance handling, or how a documented value of 0 (unknown) is treated — notable since there is no output schema.

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 in German with an English gloss; no filler. The bilingual duplication is redundant but adds little cost and no ambiguity.

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 two-parameter read-only check with full schema coverage, the basics are present, but with no output schema the description should say what the comparison returns (pass/fail, margin, unknown threshold) and it does not.

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 both parameters are already fully documented including ranges and the meaning of 0. The description only restates the two roles (measured flow, documented activation threshold) without adding semantics beyond the schema; 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?

States a concrete operation: compare the measured shower flow (observed_l_min) against the heater's documented activation threshold. A reader knows exactly what comparison happens, though it never names the sibling tools it differs from (e.g. duschdurchfluss_messen, which only measures).

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 purpose implies when the tool applies — after a flow measurement exists and a heater threshold is documented — but there is no explicit when-to-use/when-not guidance and no statement about what to do if the documented value is unknown (0).

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