Skip to main content
Glama

getecoback-raumklima

spuelbecken_kaltfuellung_stufenwechsel_zeitpunkt

Read-only

Bei zwei vermessenen Kaltwasserstufen bestimmen, in welchem beobachteten Abschnitt die geplante Beckenfüllung erreicht wurde — Locate a basin fill mark within a measured two-rate cold-water sequence.

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": {
      "ziel_l": "<ziel_l>",
      "erste_fuellung_l": "<erste_fuellung_l>",
      "erste_dauer_s": "<erste_dauer_s>",
      "zweite_rate_l_min": "<zweite_rate_l_min>",
      "zweite_dauer_s": "<zweite_dauer_s>"
    },
    "name": "spuelbecken_kaltfuellung_stufenwechsel_zeitpunkt"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_lYesEigene Zielmenge in Litern bis zum vorgesehenen Füllstrich.
erste_dauer_sYesGemessene Dauer bis zum Stufenwechsel in Sekunden.
zweite_dauer_sYesBis zum Ende tatsächlich erfasste Dauer der zweiten Stufe in Sekunden.
erste_fuellung_lYesMenge beim Wechsel von der ersten auf die zweite beobachtete Stufe.
zweite_rate_l_minYesSeparat bei derselben Stufe gemessene Liter pro Minute.

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 readOnlyHint=true and openWorldHint=false, so safety and closed-world scope are covered by structured data. The description adds that this is an interpolation/location over supplied measurements rather than a measurement itself, which is useful, but it says nothing about what happens when the target falls outside the observed sequence or how the answer is expressed.

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?

Two short sentences, but the German and English versions are near-duplicates conveying the same content, which is pure redundancy rather than front-loading new information. The opening does state the core task first, so it is not disorganized, but the bilingual doubling costs space for no added clarity.

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?

This is a five-required-parameter computation tool with no output schema, so the description carries the burden of explaining the result. It hints at the result ('in welchem beobachteten Abschnitt') but never specifies whether the answer is an interval index, a time offset, or a volume, nor what is returned if the target is unreachable — a meaningful gap for a deterministic calculator.

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 units, ranges and per-field meanings already documented (target liters, stage-one fill, stage durations, second-stage rate). The description only echoes the two-stage framing and adds no interpretation of how the rate and fill quantities combine, so the 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?

The description names a concrete operation: determine in which observed interval the planned basin fill level was reached given a measured two-stage cold-water fill. The English sentence ('Locate a basin fill mark within a measured two-rate cold-water sequence') reinforces a specific verb+resource. It does not differentiate itself from any sibling, and the domain phrasing is dense, 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?

The only implied condition is that two cold-water stages must already have been measured ('Bei zwei vermessenen Kaltwasserstufen'), which is a prerequisite rather than guidance on when to reach for this tool over a sibling. There is no statement of when not to use it, no named alternative, and no note about what to do if the target was never reached.

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