Skip to main content
Glama

getecoback-climate-weather

poolroboter_korb_pflegezeitfenster

Read-only

Vorhandene Korbpflege als Teil der geplanten Poolnutzung prüfen — Reserve a post-run window for cleaning and storing the pool-robot filter basket.

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": {
      "pickup_min": "<pickup_min>",
      "basket_min": "<basket_min>",
      "storage_min": "<storage_min>",
      "available_min": "<available_min>",
      "same_conditions": "<same_conditions>"
    },
    "name": "poolroboter_korb_pflegezeitfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
basket_minYesBeobachtete Minuten für die freigegebene Korbreinigung.
pickup_minYesBeobachtete Minuten für Entnahme und Entwässerung an der vorgesehenen Stelle.
storage_minYesBeobachtete Minuten zum Wegräumen oder zur erforderlichen Lagerung nach Anleitung.
available_minYesZeit zwischen Laufende und nächster Poolnutzung oder Aufräumfrist.
same_conditionsYesVergleichbare Schmutzlast, gleiches Modell und gleiche Nutzung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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; the description should then explain the comparison logic (what threshold with same_conditions makes the window valid) and whether anything is persisted. Instead it uses the word 'Reserve', which reads like a write action and sits awkwardly against readOnlyHint=true, without clarifying that this is a pure assessment.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and front-loaded, but it switches mid-sentence from German to English, mixing 'prüfen' with 'Reserve', which is the main source of ambiguity. One clean sentence stating the computation would be tighter and clearer.

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

Completeness2/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 is the only place that could say what comes back (a boolean fit verdict? leftover minutes?) — and it does not. For a tool requiring five inputs with a comparison rule, the description omits the decision rule and the result shape entirely.

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 a German description, so the schema does the heavy lifting. The tool description adds no meaning beyond it — it does not explain how pickup_min, basket_min and storage_min combine, nor what same_conditions gates — which is the baseline 3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description combines two framings — 'Vorhandene Korbpflege ... prüfen' (a feasibility check) and 'Reserve a post-run window' (an allocation) — so the agent cannot tell whether this tool computes a fit or records a reservation. The resource (cleaning/storing the pool-robot filter basket after a run) is identifiable, but the verb is muddled and the close sibling poolroboter_entnahme_fenster is never distinguished.

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?

The description gives no when-to-use context and never mentions the related entry (poolroboter_entnahme_fenster) that an agent would have to choose between. The only implicit guidance comes from the input schema's observed-vs-available minutes, not from the description text.

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