Skip to main content
Glama

getecoback-raumklima

poolroboter_beckencheck

Read-only

Beckenform, Schmutz und Korbpflege vor der Auswahl eines Poolroboters prüfen — Assess debris, obstacles and basket care for a pool robot.

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": {
      "debris": "<debris>",
      "obstacle": "<obstacle>",
      "care": "<care>"
    },
    "name": "poolroboter_beckencheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
careYesKorb im Alltag zugänglich und leicht zu reinigen?
debrisYesVorherrschendes Material: Blätter, fein, grüne Ablagerung oder unbekannt.
obstacleYesBodenstrecke frei, Treppen oder unbekannt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, closed-world check, and the description adds the decision context of pre-selection assessment. However, it does not explain what the assessment produces or how the inputs affect the conclusion.

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

Conciseness5/5

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

The definition is a single front-loaded sentence with no unnecessary elaboration. The German and English phrasing are compact and immediately actionable.

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?

For a simple three-parameter read-only check, the inputs and usage context are adequately covered. The main gap is that there is no output schema and the description does not say what kind of result or recommendation the assessment returns.

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 coverage is 100%, and all three enum parameters are already described in the input schema. The description only restates the assessment categories at a high level, adding little beyond the structured parameter descriptions.

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 uses a specific verb ('prüfen/assess') and names the resources being checked: debris, obstacles and basket care. It also frames the tool as preparation for selecting a pool robot, though it does not explicitly distinguish itself from any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the timing: use this before choosing a pool robot. There are no explicit exclusions or named alternatives, so it stops short of full routing guidance.

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