Skip to main content
Glama

getecoback-climate-weather

entfeuchter_standzeit_ereignis_wartefenster

Read-only

Eine noch laufende Wartezeit nach dem Abschalten mit einer früheren gemessenen Wiederanlaufpause vergleichen — Distinguish a still-censored off interval from an observed delay.

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": {
      "referenz_pause_min": "<referenz_pause_min>",
      "fenster_bis_jetzt_min": "<fenster_bis_jetzt_min>",
      "wiederanlauf_min": "<wiederanlauf_min>",
      "wieder_an": "<wieder_an>",
      "gleiches_protokoll": "<gleiches_protokoll>"
    },
    "name": "entfeuchter_standzeit_ereignis_wartefenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
wieder_anYesWurde innerhalb des Fensters ein aktueller Wiederanlauf tatsächlich beobachtet?
wiederanlauf_minYesAktuelle Minuten bis zum beobachteten Wiederanlauf, sonst 0.
gleiches_protokollYesSind Auslöser, Einstellung und Messmethode der Pausen vergleichbar?
referenz_pause_minYesFrühere vollständig beobachtete Pause zwischen Abschalten und Wiederanlauf.
fenster_bis_jetzt_minYesAktueller Beobachtungszeitraum seit dem Abschalten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 and the description needn't restate it. The description does add the meaningful behavioral distinction between censoring and observed delay, which is the actual logic of the tool. It says nothing about what the comparison yields or whether the result depends on gleiches_protokoll being true, so the transparency gain is partial.

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?

Two short clauses, front-loaded with the core action before the clarifying restatement, with no filler. The bilingual duplication costs a little length but makes the intent unambiguous.

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 five required parameters, no output schema, and a purely computational purpose, the description should indicate what kind of answer comes back (a ratio, a verdict, a boolean) and how a false gleiches_protokoll is handled. It covers the concept adequately but leaves the return behavior entirely to inference, which is a real gap for a no-output-schema tool.

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 with units and bounds. The description introduces the censoring-versus-observed distinction that motivates wieder_an and wiederanlauf_min, but adds no syntax, default, or interaction detail beyond the schema. Baseline 3 applies when the schema carries the parameter semantics.

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 (compare a currently censored waiting interval against an earlier, fully observed restart pause) and states the conceptual outcome it produces — separating a censored from an observed delay. The verb and resource are identifiable, though it never differentiates itself from adjacent tools such as entfeuchter_mindestpause_zeitplan or warmwasser_neustart_standzeit_ueberfluss.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only cue is the implicit framing 'Distinguish a still-censored off interval from an observed delay', which lets an agent infer the scenario but not the boundary conditions (e.g. needing a comparable earlier pause).

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