Skip to main content
Glama

getecoback-climate-weather

saugroboter_zonen_faelligkeit

Read-only

Fällige Raumreinigung für wiederkehrende Läufe aus deiner eigenen Taktung ableiten — Decide which zones are due under a household cleaning cadence.

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": {
      "flur_tage": "<flur_tage>",
      "flur_intervall": "<flur_intervall>",
      "wohnraum_tage": "<wohnraum_tage>",
      "wohnraum_intervall": "<wohnraum_intervall>"
    },
    "name": "saugroboter_zonen_faelligkeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
flur_tageYesVergangene Tage seit Kontrolle und Reinigung des Flurs.
wohnraum_tageYesVergangene Tage seit Kontrolle und Reinigung des Wohnraums.
flur_intervallYesEigenes Prüfintervall für den Flur in Tagen.
wohnraum_intervallYesEigenes Prüfintervall für Wohnräume in Tagen.

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 agent knows this is a safe local computation. The description adds that the cadence is user-supplied rather than learned, which is useful, but says nothing about what constitutes 'due' (threshold comparison, equal-to-interval behavior) or whether any state is stored.

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?

One compact sentence, front-loaded with the outcome, with no filler. The bilingual duplication is slightly redundant but arguably aids disambiguation for mixed-language agents.

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?

There is no output schema, so the description should explain the shape of the answer — which zones come back and in what form. As written, an agent must call it blind to learn whether it returns booleans per zone, a ranked list, or free text.

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% and all four numeric parameters carry their own descriptions, so the schema does the work. The description only hints that the intervals are 'deine eigene Taktung' and adds no detail on units, edge cases, or how days-since versus interval interact.

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?

States a specific decision task: derive which rooms/zones are due given the user's own cadence. The German verb phrase 'Fällige Raumreinigung ... ableiten' plus the English gloss makes the function clear. Minor mismatch: it says 'zonen' but the parameters cover only two named areas (Flur, Wohnraum), which slightly blurs scope.

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?

No statement of when to prefer this over sibling scheduling aids such as saugroboter_restaufgaben_verteilen or saugroboter_manuelle_zeit, and no prerequisites or exclusions. Usage must be inferred entirely from the title of the task.

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