Skip to main content
Glama

getecoback-raumklima

saugroboter_teppich_wischmodus

Read-only

Wischroute bei Teppichen, Fransen und fehlender Bodenfreigabe planen — Resolve carpet avoidance and dry vacuuming on a mixed-floor route.

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": {
      "floor_permission": "<floor_permission>",
      "carpet": "<carpet>",
      "separation": "<separation>"
    },
    "name": "saugroboter_teppich_wischmodus"
  }
}

Input Schema

NameRequiredDescriptionDefault
carpetYesTeppich auf dem Roboterweg.
separationYesSichere Trennung von Teppich und Wischbetrieb laut Anleitung und Einrichtung geprüft?
floor_permissionYesFreigabe des Hartbodens fürs Wischen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

While annotations cover safety (readOnly), the description adds critical behavioral information by stating that the function's core task is to 'Resolve' complex conflicts, which goes beyond merely defining input parameters. It describes the nature of the outcome.

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 description is a concise, highly effective single statement using an em dash to clearly separate the operation from the specific real-world problem it solves, resulting in zero wasted language.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition is highly complete for its niche. It explains the 'what' (route planning), the 'how' (resolving avoidance/dry vacuuming), and the 'why' (mixed floor complexities), providing maximum value despite having no output schema to describe.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema coverage is 100%, the description does not need to define the inputs. However, it provides strong semantic context by linking the required parameters to the overall goal of resolving the complex mixed-floor cleaning problem.

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

Purpose5/5

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

The tool clearly defines its purpose as planning a specific cleaning route (Wischroute planen) in complex scenarios involving carpets, fringes, and permission statuses.

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?

The description provides strong usage context by specifying that the tool is used to 'resolve carpet avoidance and dry vacuuming on a mixed-floor route.' This clearly sets the appropriate operational context for calling the tool.

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