Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_play

Start or resume cleaning with your Eufy RoboVac vacuum cleaner to maintain floor cleanliness.

Instructions

Start/resume robovac cleaning

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the robovac_play tool. It ensures the RoboVac instance is initialized and calls the play() method on the RoboVac object to start or resume cleaning.
    case "robovac_play":
      this.ensureRoboVacInitialized();
      await this.robovac!.play();
      return {
        content: [
          {
            type: "text",
            text: "RoboVac started/resumed cleaning!",
          },
        ],
      };
  • src/server.ts:149-156 (registration)
    Registration of the robovac_play tool in the ListTools response, defining its name, description, and empty input schema (no parameters required).
    {
      name: "robovac_play",
      description: "Start/resume robovac cleaning",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for the robovac_play tool, specifying an empty object (no input parameters required).
    inputSchema: {
      type: "object",
      properties: {},
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't cover permissions, side effects, response format, or error handling, leaving significant gaps for a tool that likely controls hardware.

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, efficient phrase ('Start/resume robovac cleaning') with zero wasted words. It's front-loaded and perfectly sized for the tool's purpose.

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 no annotations, no output schema, and a simple tool, the description is incomplete. It lacks context on prerequisites (e.g., connection state), behavioral outcomes, or error scenarios, which are crucial for safe invocation in a sibling-rich environment.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, but this is appropriate given the tool's simplicity, warranting a baseline score above minimum viable.

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/resume') and resource ('robovac cleaning'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'robovac_start_cleaning' or 'robovac_pause', which prevents 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?

No guidance is provided on when to use this tool versus alternatives like 'robovac_start_cleaning' or 'robovac_pause'. The description implies usage for starting or resuming cleaning, but lacks explicit context or exclusions.

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