Skip to main content
Glama

getecoback-raumklima

duschdurchfluss_messen

Read-only

Duschdurchfluss aus aufgefangener Wassermenge und Zeit bestimmen — Compute shower flow from a bucket measurement.

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": {
      "litres": "<litres>",
      "seconds": "<seconds>"
    },
    "name": "duschdurchfluss_messen"
  }
}

Input Schema

NameRequiredDescriptionDefault
litresYesAufgefangenes Volumen in Litern.
secondsYesMesszeit in Sekunden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 side-effect profile is covered, and the description is consistent with a pure calculation. However, it adds no behavioral context beyond the annotations — notably it never says what the tool returns or in what unit (L/min), which for a calculator is the single most useful piece of behavior to disclose.

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?

Very short and front-loaded, with the core action in the first clause. The second sentence is a near-verbatim English translation of the first, which is mild redundancy rather than added information.

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 simple two-parameter calculation with a fully documented schema, most of the burden is already carried by structured fields. Since there is no output schema, the missing statement of what is returned (presumably flow in litres per minute) leaves a real gap an agent would otherwise have to guess at.

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 both parameters documented including units and min/max bounds, so the baseline is 3. The description only restates the two inputs in prose ('aufgefangene Wassermenge und Zeit') without adding format or interpretation guidance beyond the schema.

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 specific verb and resource: determining shower flow from collected water volume and elapsed time, with the method (bucket measurement) spelled out. An agent can tell it is a measurement/calculation tool rather than a data lookup. It does not differentiate itself from nearby siblings (e.g. duschwasser_mischverhaeltnis), 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The bucket-measurement phrasing implies a physical measurement scenario, but the agent must infer that on its own.

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