Skip to main content
Glama

getecoback-raumklima

wassergruppen_ueberlappung_mindestdurchfluss

Read-only

Bei einem protokollierten Mehrgeräteversuch prüfen, welche Nutzung nur während der Überlagerung unter ihrem gewählten Mindestdurchfluss lag — Compare individual solo and overlapping water flows against distinct task requirements.

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_allein_l_min": "<a_allein_l_min>",
      "b_allein_l_min": "<b_allein_l_min>",
      "a_parallel_l_min": "<a_parallel_l_min>",
      "b_parallel_l_min": "<b_parallel_l_min>",
      "a_mindest_l_min": "<a_mindest_l_min>",
      "b_mindest_l_min": "<b_mindest_l_min>"
    },
    "name": "wassergruppen_ueberlappung_mindestdurchfluss"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_allein_l_minYesVor Ort gemessener Durchfluss A ohne B.
b_allein_l_minYesVor Ort gemessener Durchfluss B ohne A.
a_mindest_l_minYesSelbst gewähltes Vergleichsminimum für Aufgabe A.
b_mindest_l_minYesSelbst gewähltes Vergleichsminimum für Aufgabe B.
a_parallel_l_minYesDurchfluss A während desselben gemeinsamen Versuchsfensters.
b_parallel_l_minYesDurchfluss B während desselben Fensters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 safety is covered. The description adds genuine behavioral value by disclosing the conditional logic — it flags only the usages that dropped below their minimum during overlap, not those failing solo — but says nothing about what the result looks like, whether a full per-device breakdown or just a flag list is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the operative condition front-loaded, which is good structure, but the German clause and the following English restatement say largely the same thing twice, so half the text is redundant and the language switch adds friction rather than detail.

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 six-parameter read-only analytic tool with no output schema, the definition covers inputs and the concept being tested but leaves the result shape unspecified — an agent knows what to pass but not whether to expect per-task verdicts, slack values, or a boolean. Adequate but with a real gap where an output schema does not compensate.

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% and each of the six required parameters carries an explicit German description (solo flow, parallel flow, self-chosen minimum per task). The description only echoes those concepts at a high level and adds no unit conventions, tolerance behavior, or guidance on the 0-100 bounds 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?

Names a concrete operation (check which usage fell below its chosen minimum flow only during overlap) on a concrete resource (a logged multi-device trial with solo and parallel flow measurements). An agent can grasp what the tool computes, though the description never contrasts it with the related minimum-flow sibling, so differentiation rests on the name alone.

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 opening clause 'Bei einem protokollierten Mehrgeräteversuch' establishes the required context: this tool applies to data from a logged multi-device experiment with solo and simultaneous measurements. That is useful implied scoping, but there is no explicit when-not guidance, no preconditions about prerequisite data, and no alternative tool named for the simpler per-device case.

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