Skip to main content
Glama

getecoback-climate-weather

saugroboter_dockbesuch_ruhefenster

Read-only

Bei einer ruhigen Zeit getrennt prüfen, ob ein erwarteter Dockbesuch Fahren, Absaugung oder beides hineinlegt. — Find the parts of a documented dock visit that extend into quiet hours.

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": {
      "retour_min": "<retour_min>",
      "ankunft_min": "<ankunft_min>",
      "ende_absaugung_min": "<ende_absaugung_min>",
      "ruhe_start_min": "<ruhe_start_min>",
      "ruhe_ende_min": "<ruhe_ende_min>"
    },
    "name": "saugroboter_dockbesuch_ruhefenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
retour_minYesErwarteter Beginn der Rückfahrt auf einer gemeinsamen Minutenachse ab Tagesbeginn.
ankunft_minYesErwartete Ankunft an der Station auf derselben Achse.
ruhe_ende_minYesEnde der Ruhezeit auf derselben Achse.
ruhe_start_minYesBeginn der bewusst freigehaltenen Ruhezeit auf derselben Achse.
ende_absaugung_minYesBeobachtetes Ende der Absaugung. Bei deaktivierter Funktion gleich Ankunft.

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 safety is covered; the description adds that evaluation is done separately for driving, suction, and their combination. It does not say what the answer looks like (per-phase flags, overlap intervals, or a verdict) and there is no output schema to fill that gap.

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 sentences, purpose first, with no filler. The English half largely restates the German, which costs a little space but aids accessibility, and the phrase 'hineinlegt' is slightly informal for a precise overlap computation.

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?

Inputs are fully documented in the schema and the tool is a closed, deterministic computation, so little is missing. However, with no output schema the description should clarify the return shape of 'die Teile … die in die Ruhezeit hineinragen', which it leaves ambiguous.

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 coverage is 100%, including the non-obvious rule that ende_absaugung_min equals ankunft_min when the suction function is disabled, so the schema does the heavy lifting. The description contributes the framing that all five values live on one shared minute axis and that phases are judged independently, but adds no format or boundary conventions beyond that.

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 verb (check whether a documented dock visit intrudes into quiet hours) and a concrete resource (the visit phases driving / suction / both against a quiet window). The phase decomposition is specific enough to distinguish it from generic scheduling tools, but it never names or contrasts a sibling such as strompreis_zwei_geraete_ruhefenster, so it stops short of 5.

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: 'getrennt prüfen' signals a per-phase evaluation of an already-documented visit, which suggests it is a downstream check rather than a planner. There is no statement of when to prefer this over the related quiet-window or scheduling siblings, and no prerequisites (e.g. that the visit must already be known) are 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