Skip to main content
Glama

getecoback-raumklima

warmwasser_erholung_zwei_gepruefte_pausen

Read-only

Kürzere der beobachteten brauchbaren Erholungspausen vor einer Folgeentnahme auswählen — Pick the shortest observed acceptable recovery gap.

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": {
      "kurze_pause_min": "<kurze_pause_min>",
      "lange_pause_min": "<lange_pause_min>",
      "kurz_ziel_erreicht": "<kurz_ziel_erreicht>",
      "lang_ziel_erreicht": "<lang_ziel_erreicht>",
      "gleiche_versuche": "<gleiche_versuche>"
    },
    "name": "warmwasser_erholung_zwei_gepruefte_pausen"
  }
}

Input Schema

NameRequiredDescriptionDefault
kurze_pause_minYesKürzerer getesteter Abstand nach derselben Vorentnahme.
lange_pause_minYesLängerer getesteter Abstand.
gleiche_versucheYesVorentnahme, Folgeentnahme und gewähltes Ziel waren vergleichbar.
kurz_ziel_erreichtYesZiel während der ganzen Folgeentnahme nach kurzer Pause beobachtet?
lang_ziel_erreichtYesZiel während der ganzen Folgeentnahme nach langer Pause beobachtet?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the result is a selection among observed acceptable pauses, but it does not disclose the decision rule (e.g. what happens if neither or both targets were reached) or what 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.

Conciseness4/5

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

A single front-loaded sentence states the core selection rule with no filler. The German/English duplication is slightly redundant but does not obscure the intent.

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 five-parameter decision tool with no output schema, the description does not explain the return value or edge-case behavior. Annotations and the fully documented schema compensate partially, but the selection logic and output shape remain unstated.

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 five parameters are already documented in the schema. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 gives a concrete verb and resource: pick the shortest observed acceptable recovery gap before a follow-up draw. An agent can understand it is a selection/tie-break operation over two tested pause lengths, though the domain-specific German phrasing ("beobachteten brauchbaren Erholungspausen") is not differentiated from the many warm-water siblings.

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?

Usage is only implied: it presumes the caller already has two tested pause lengths and goal observations. There is no explicit statement of when to use this versus another warm-water tool, no prerequisites, and no exclusion conditions.

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