Skip to main content
Glama

getecoback-climate-weather

saugwischer_bedienphasen_pausenfenster

Read-only

Abschnitte einer Wischrunde mit der selbst gewünschten Pausenlänge abgleichen — Find which active stages exceed a household’s chosen uninterrupted-work window.

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": {
      "vorbereiten_min": "<vorbereiten_min>",
      "wischabschnitt_min": "<wischabschnitt_min>",
      "nachpflege_min": "<nachpflege_min>",
      "eigenes_zeitfenster_min": "<eigenes_zeitfenster_min>"
    },
    "name": "saugwischer_bedienphasen_pausenfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
nachpflege_minYesLängster nicht aufgeteilter aktiver Pflegeabschnitt laut Ablauf.
vorbereiten_minYesGemessene aktive Zeit zum Bereitstellen.
wischabschnitt_minYesLängster tatsächlich zusammenhängender Wischabschnitt.
eigenes_zeitfenster_minYesSelbst gewünschte maximale zusammenhängende Dauer, in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the tool evaluates/compares rather than producing a schedule, and that its finding is which stages exceed the window, which is useful beyond the annotations. It does not state whether the comparison is strict-greater-than or inclusive, nor what the response looks like, in a tool with no output schema.

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 sentences, front-loaded with the German statement of scope followed by an English gloss. The bilingual duplication is intentional for audience coverage rather than padding, and there is no filler. Slight redundancy between the two halves keeps it off a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-number, read-only comparison with no output schema and no nested objects, the description gives enough to call it correctly and hints at the result (which stages exceed the window). The main residual gap is the exact comparison semantics and the shape of the returned finding, which the agent cannot derive elsewhere.

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 numeric inputs are already self-documented with min/max bounds and per-field meaning. The description only glosses eigenes_zeitfenster_min as the household's chosen uninterrupted-work window, adding nothing new about vorbereiten_min, wischabschnitt_min, or nachpflege_min. Baseline 3 is appropriate 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 names a specific verb and resource: comparing sections of a wiping round against a self-chosen pause length, and rephrases it in English as finding active stages that exceed the household's uninterrupted-work window. This is far more than a restatement of the name. It does not explicitly contrast itself with siblings such as wartezeit_nachpflege or tankstopps_planen, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The comparison framing implies when the tool is applicable (when you know the three stage durations and a desired window), but there is no explicit when-to-use/when-not wording and no named alternative. An agent must infer the trigger condition from the phrasing alone.

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