Skip to main content
Glama

getecoback-raumklima

warmwasser_anlauf_abbruch_ziel_ungemessen

Read-only

Eine abgebrochene Warmwasserprobe als Untergrenze statt als erreichte Wartezeit festhalten — Keep a stopped trial as a censored observation.

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": {
      "beobachtet_s": "<beobachtet_s>",
      "ziel_erreicht": "<ziel_erreicht>",
      "ziel_sekunde": "<ziel_sekunde>",
      "plan_grenze_s": "<plan_grenze_s>"
    },
    "name": "warmwasser_anlauf_abbruch_ziel_ungemessen"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtet_sYesLänge des lückenlos beobachteten Versuchs ab Öffnen.
ziel_sekundeYesBeobachteter Sekundenwert beim Erreichen. Ohne beobachtetes Ziel 0.
plan_grenze_sYesEigene Vergleichszeit, bis zu der das Ziel erreicht sein soll.
ziel_erreichtYesWurde der selbst gesetzte Zielzustand tatsächlich 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 contributes the genuinely behavioral idea of censoring — the recorded value is a lower bound, not a measurement — which is real context beyond the annotations. It does not, however, clarify whether calling this persists a record ("festhalten" reads like a write, which sits uneasily with readOnlyHint, though it can also mean "treat as") or what is returned, leaving an ambiguity worth resolving.

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 that puts the condition (aborted trial) before the framing (lower bound rather than measured wait). The bilingual duplication costs some tokens, but for a German-named tool with German parameter names it improves accessibility rather than wasting space. No filler sentences.

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?

With four required parameters, full schema coverage, and no output schema, the description covers the core semantic of the call adequately. It is still thin on what the call produces and how the result should be reported downstream, and it gives no route to the sibling for completed trials, which matters in a family of many closely named warm-water tools.

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 four parameters are already documented, which sets the baseline at 3. The description adds interpretive meaning for the ziel_erreicht / ziel_sekunde combination (a false flag with zero target second means the trial was censored), but it does not address plan_grenze_s or the relationship between beobachtet_s and plan_grenze_s, so it only marginally exceeds 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?

The description names a concrete operation on a concrete object: record a stopped warm-water trial ("abgebrochene Warmwasserprobe") as a censored observation/lower bound rather than as an achieved wait time. That core distinction is specific and lets an agent separate this from tools that record achieved values. It falls short of 5 because it does not name or point at the sibling used for a completed trial, so the differentiation is conceptual rather than explicit.

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 trigger condition is implied clearly (trial was aborted, target not reached), and the phrase "statt als erreichte Wartezeit" hints at the alternative path. However, no sibling tool is named, there is no explicit when-not clause, and nothing states prerequisites or what to do when the target actually was observed. Usage is inferable but not spelled out.

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