Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_start_cleaning

Initiate a cleaning cycle for your Eufy RoboVac vacuum cleaner to clean floors automatically.

Instructions

Start the robovac cleaning cycle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for robovac_start_cleaning tool: Ensures RoboVac is initialized and calls startCleaning() method.
    case "robovac_start_cleaning":
      this.ensureRoboVacInitialized();
      await this.robovac!.startCleaning();
      return {
        content: [
          {
            type: "text",
            text: "RoboVac cleaning started!",
          },
        ],
      };
  • src/server.ts:344-351 (registration)
    Registration of the robovac_start_cleaning tool in the listTools response, including name, description, and empty input schema.
    {
      name: "robovac_start_cleaning",
      description: "Start the robovac cleaning cycle",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for robovac_start_cleaning: empty object (no parameters).
    inputSchema: {
      type: "object",
      properties: {},
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action but lacks critical details: whether this requires the robovac to be in a specific state (e.g., charged, not already cleaning), what happens if invoked while cleaning is ongoing, if it's idempotent, or what the expected outcome is. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 single, clear sentence with no wasted words. It's front-loaded with the core action ('Start the robovac cleaning cycle'), making it immediately understandable. Every word earns its place, and there's no unnecessary elaboration or redundancy.

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?

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It doesn't address behavioral aspects like state requirements, idempotency, or error conditions. For a tool that likely changes device state, more context is needed to ensure safe and correct usage by an AI agent.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The baseline for 0 parameters is 4, as the description appropriately doesn't discuss non-existent parameters. It focuses on the action, which is sufficient given the empty input 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 clearly states the action ('Start') and target resource ('robovac cleaning cycle'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'robovac_pause', 'robovac_stop_cleaning', and 'robovac_return_home' by specifying initiation of cleaning. However, it doesn't explicitly differentiate from 'robovac_play' which might have overlapping functionality, preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether the robovac must be connected or initialized first), nor does it clarify relationships with siblings like 'robovac_play' or 'robovac_set_work_mode'. Without such context, the agent must infer usage from tool names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/appleton/sam'

If you have feedback or need assistance with the MCP directory API, please join our Discord server