Skip to main content
Glama

getecoback-raumklima

saugroboter_akkupause_zeitfenster

Read-only

Gesamtdauer einer beobachteten Roboterrunde inklusive Zwischenladen testen — Check whether a robot run with a recharge fits a home availability 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": {
      "cleaning_min": "<cleaning_min>",
      "recharge_min": "<recharge_min>",
      "return_min": "<return_min>",
      "available_min": "<available_min>",
      "comparable": "<comparable>"
    },
    "name": "saugroboter_akkupause_zeitfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
comparableYesGleiche Route, Geräteeinstellungen, Akkustand zu Beginn und ähnliche Laufbedingungen?
return_minYesZusätzlicher Stationsweg oder erneute Anfahrt, soweit nicht bereits eingerechnet.
cleaning_minYesFahr- und Reinigungszeit laut eigener Runde, ohne Pausen.
recharge_minYesGemessene Wartezeit beim Zwischenladen. Ohne Zwischenladen 0 eintragen.
available_minYesZeitraum, in dem alle Zielräume zugänglich sind.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 and locality are covered. The description adds the substantive scope note that the total includes intermediate charging and is judged against the availability window, but it never says what the tool returns (a verdict, a margin, minutes of overshoot) despite there being 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?

A single tight sentence, front-loaded with the outcome being tested. The German/English duplication of the same statement is slightly redundant but aids disambiguation for bilingual agents.

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?

With five required numeric/boolean inputs and no output schema, the description plus the fully documented schema supply everything needed to invoke it. The only real gap is the absence of any statement about the result format, which would matter for an agent planning downstream steps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every parameter carries a precise German explanation including the edge case 'Ohne Zwischenladen 0 eintragen'. The description adds the framing that these values are summed into one observed round duration, which is the meaning an agent needs to map inputs correctly.

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 operation (test total duration of an observed robot run including intermediate charging) and its decision context (does it fit a home availability window). It is clearly distinct from the sibling helpers, though it does not explicitly name any sibling to differentiate against.

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?

Use is implied by the verb 'testen / Check whether ... fits' — an agent can infer this is a feasibility check for a run with recharging. There is no explicit when-not condition, no prerequisite (e.g. that measurements must already exist), and no pointer to alternatives such as the manual-time or distribution siblings.

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