Skip to main content
Glama

getecoback-raumklima

saugroboter_staubbeutel_nutzungsplan

Read-only

Beutelwechsel an einer konkreten Roboterstation auf eigene Nutzungswochen umlegen — Estimate planned bag stock from observed runs per change.

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": {
      "laeufe_pro_woche": "<laeufe_pro_woche>",
      "laeufe_je_beutel": "<laeufe_je_beutel>",
      "wochen": "<wochen>",
      "volle_beutel_vorhanden": "<volle_beutel_vorhanden>"
    },
    "name": "saugroboter_staubbeutel_nutzungsplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
wochenYesBetrachtungszeitraum in Wochen.
laeufe_je_beutelYesEigener beobachteter Durchschnitt an Läufen je Beutelwechsel.
laeufe_pro_wocheYesErwartete Läufe je Woche.
volle_beutel_vorhandenYesUnbenutzte, bereits passende Beutel am Start.

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 safety is covered. The description adds that the result is an estimate derived from the user's own observed runs per change, which is meaningful context about the nature of the output. It does not describe the shape of the returned plan (bag count, change points, or timeframe), which matters since there is 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 front-loaded sentence with the core constraint stated first; the German/English doubling is mildly redundant but short and does aid clarity. No filler or boilerplate.

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?

All four parameters are required numeric inputs and the tool returns a computed estimate with no output schema, so the description should say what the plan contains. It conveys the estimation basis but not the returned quantities, leaving a gap for a pure calculation tool.

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 has a German description plus min/max bounds, so the schema carries the semantic load. The description echoes two of them (observed runs per change, usage weeks) but adds no syntax, unit, or edge-case guidance beyond the schema.

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 states a specific task: converting bag changes at a concrete robot station onto the user's own usage weeks and estimating planned bag stock from observed runs per change. An agent can tell this is a stock/interval projection rather than a physical inspection. It stops short of naming the closest sibling (saugroboter_absaugstation_beutelkontrolle), so differentiation is left implicit.

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 explicit when-to-use statement, no prerequisites, and no named alternative. The phrase 'auf eigene Nutzungswochen umlegen' hints that this is for planning rather than checking, but an agent must infer that versus the bag-check sibling.

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