Skip to main content
Glama

getecoback-raumklima

poolroboter_entnahme_fenster

Read-only

Nasse Entnahme und Korbzugang vor einem wiederkehrenden Poolroboterlauf einplanen — Check the observed lifting load and handling route for routine pool-robot retrieval.

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": {
      "wet_mass_kg": "<wet_mass_kg>",
      "planned_limit_kg": "<planned_limit_kg>",
      "documented_route": "<documented_route>",
      "measured": "<measured>"
    },
    "name": "poolroboter_entnahme_fenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredYesGewicht aus sicherer, dokumentierter Entnahmesituation bekannt?
wet_mass_kgYesNasse Masse bei Entnahme nach Geräteanleitung, falls sie bereits sicher gemessen wurde.
documented_routeYesVorgesehener Griff und trockener, zugänglicher Weg zur Pflege laut Anleitung geklärt?
planned_limit_kgYesSelbst gewählter Planungswert für diese Handhabung, keine ergonomische Freigabe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 and the description is consistent with it. What the description fails to add is any behavioral substance: it does not say what the tool actually produces (a verdict, a planning window, a warning?), how the measured=false branch behaves, or that planned_limit_kg is explicitly non-authoritative. For a read-only evaluation tool whose whole value is its output, this is thin.

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 definition is short and front-loads the situational context, which is good. However, the German sentence and the English sentence restate nearly the same content rather than complementing each other, so roughly half the text is redundant, and neither half names a concrete action or outcome.

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 4 required, fully schema-documented parameters and no output schema, an agent has enough to construct a call. What is missing is the payoff side: without an output schema, the description should state what the check returns or how the four inputs combine into a result, and it does not.

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 all four parameters are documented in the schema, so the baseline is 3. The description gestures at two of them ('lifting load' ~ wet_mass_kg, 'handling route' ~ documented_route) but adds no format, threshold, or interpretation guidance beyond the schema text, and says nothing about planned_limit_kg or measured.

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 gives a verb-plus-resource combination ('Nasse Entnahme und Korbzugang ... einplanen' / 'Check the observed lifting load and handling route'), so the general area is identifiable. But 'Entnahme' and 'Fenster' stay abstract, and nothing distinguishes this from the sibling poolroboter_korb_pflegezeitfenster or poolroboter_beckencheck. The German/English duplication further blurs rather than sharpens the stated purpose.

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?

Usage is only implied through the timing phrase 'vor einem wiederkehrenden Poolroboterlauf' and 'for routine pool-robot retrieval'. That tells the agent the context (planning ahead of a recurring run) but gives no when-not conditions, no prerequisites, and no signal about which of the sibling planning tools should be chosen instead.

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