Skip to main content
Glama

getecoback-raumklima

duschdurchfluss_vergleich_menge_zeitband

Read-only

Mehrere Eimertests anhand ihrer Mengen- und Zeitgrenzen auf eine verlässlich höhere Durchflussrate prüfen — Compare flow ranges from independently bounded volumes and durations.

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": {
      "a_min_l": "<a_min_l>",
      "a_max_l": "<a_max_l>",
      "a_min_s": "<a_min_s>",
      "a_max_s": "<a_max_s>",
      "b_min_l": "<b_min_l>",
      "b_max_l": "<b_max_l>",
      "b_min_s": "<b_min_s>",
      "b_max_s": "<b_max_s>"
    },
    "name": "duschdurchfluss_vergleich_menge_zeitband"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_max_lYesGrößte mögliche Menge in Test A.
a_max_sYesLängste mögliche Dauer A.
a_min_lYesKleinste mögliche Menge in Test A in Litern.
a_min_sYesKürzeste mögliche Dauer A in Sekunden.
b_max_lYesGrößte mögliche Menge in Test B.
b_max_sYesLängste mögliche Dauer B.
b_min_lYesKleinste mögliche Menge in Test B in Litern.
b_min_sYesKürzeste mögliche Dauer B in Sekunden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this as a read-only, closed-world operation, so the safety profile is covered. The description adds that it checks for a 'reliably higher' flow rate across independently bounded tests, but it does not disclose the return format, the method behind 'reliably', or edge-case behavior such as invalid bounds.

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 definition is short and front-loads the purpose. The bilingual duplication is not wasteful, but the German sentence is somewhat dense and the English translation largely repeats it rather than adding clarity.

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?

This is an eight-required-parameter comparison tool with no output schema, yet the description never explains what the tool returns or how the 'reliably higher' judgment is produced. It also leaves unclear whether 'Mehrere Eimertests' means more than the two test groups (A and B) that the schema actually supports.

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 eight parameters are already documented with types, ranges, and descriptions. The tool description adds no parameter-level meaning beyond restating that volumes and durations are involved, making the baseline 3 appropriate.

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 ('prüfen/compare') and resource ('Durchflussrate') and states the basis ('Mengen- und Zeitgrenzen'). It is clear enough to distinguish from a simple measurement sibling, though it does not explicitly name an alternative and the word 'Mehrere' sits awkwardly against a schema that only defines tests A and B.

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?

The description implies the tool is for comparing bounded bucket-test ranges, but it gives no explicit when-to-use guidance, no when-not-to-use guidance, and does not name any sibling as an alternative. An agent must infer the appropriate context from the one-sentence purpose.

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