Skip to main content
Glama

getecoback-climate-weather

saugroboter_manuelle_zeit

Read-only

Bisherige Handarbeit mit Vorbereitung, Eingriffen und Pflege beim Roboter vergleichen — Compare active cleaning time including robot preparation and upkeep.

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": {
      "comparable": "<comparable>",
      "manual_min": "<manual_min>",
      "setup_min": "<setup_min>",
      "intervention_min": "<intervention_min>",
      "care_min": "<care_min>",
      "runs_per_week": "<runs_per_week>"
    },
    "name": "saugroboter_manuelle_zeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
care_minYesAktive Minuten für Gerätereinigung und Tank- oder Beutelpflege.
setup_minYesAktive Minuten zum Freiräumen und Einrichten.
comparableYesGleiche Räume, Verschmutzung und Reinigungswirkung?
manual_minYesAktive Minuten ohne Roboter.
runs_per_weekYesVergleichbare Reinigungsdurchgänge pro Woche.
intervention_minYesAktive Minuten für Eingriffe und Nacharbeit.

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 is not required to carry it. The description adds conceptual framing about which cost components are included (preparation, intervention, upkeep), but says nothing about what the tool actually returns — e.g. whether it yields weekly time saved, a ratio, or a break-even — nor how the 'comparable' flag affects the result. Modest added value over annotations, hence a 3.

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 short sentence rendered in German and then English — front-loaded and free of filler, though the bilingual duplication is strictly redundant for any single reader. Nothing else is wasted.

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 six required numeric inputs, no output schema and high mutation-free complexity, the description should at minimum say what the comparison produces and how the required 'comparable' boolean gates the result. It does not, leaving the agent unable to predict the return value, though the fully documented schema prevents this from being a serious gap.

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% and every parameter carries its own German description with units and bounds, so the schema does the heavy lifting. The description's mention of Vorbereitung, Eingriffen and Pflege loosely maps to setup_min, intervention_min and care_min but adds no syntax, unit or interpretation guidance beyond the schema. Baseline 3 is correct here.

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 (compare / vergleichen) and a specific subject: manual cleaning effort with preparation, interventions and upkeep versus the robot's active time. That is more than a restatement of the tool name and tells an agent what kind of calculation this is. It stops short of differentiating itself from sibling tools such as geraetewechsel_rechnen or geraetetakt_aus_messung, which also perform cleaning-effort math.

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 statement of when this tool is appropriate versus alternatives, no prerequisite (e.g. that comparable=true is needed for a valid comparison), and no exclusions. The agent must infer the use case entirely from the title and parameter names.

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