Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_set_clean_speed

Adjust the suction power of your Eufy RoboVac to match cleaning needs, choosing from STANDARD, BOOST_IQ, MAX, or NO_SUCTION modes.

Instructions

Set the suction speed of the robovac

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
speedYesThe cleaning speed to set

Implementation Reference

  • Handler for robovac_set_clean_speed tool: ensures RoboVac is initialized, calls setCleanSpeed on the RoboVac instance with the speed argument cast to CleanSpeed type, and returns a success message.
    case "robovac_set_clean_speed":
      this.ensureRoboVacInitialized();
      await this.robovac!.setCleanSpeed(args?.speed as CleanSpeed);
      return {
        content: [
          {
            type: "text",
            text: `Clean speed set to: ${args?.speed}`,
          },
        ],
      };
  • src/server.ts:134-148 (registration)
    Registration of the robovac_set_clean_speed tool in the listTools response, including name, description, and input schema.
    {
      name: "robovac_set_clean_speed",
      description: "Set the suction speed of the robovac",
      inputSchema: {
        type: "object",
        properties: {
          speed: {
            type: "string",
            description: "The cleaning speed to set",
            enum: ["STANDARD", "BOOST_IQ", "MAX", "NO_SUCTION"],
          },
        },
        required: ["speed"],
      },
    },
  • Input schema for robovac_set_clean_speed defining the 'speed' parameter as a string enum with specific cleaning speed options.
    inputSchema: {
      type: "object",
      properties: {
        speed: {
          type: "string",
          description: "The cleaning speed to set",
          enum: ["STANDARD", "BOOST_IQ", "MAX", "NO_SUCTION"],
        },
      },
      required: ["speed"],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Set' implying a mutation, but doesn't cover critical aspects like whether this requires specific permissions, if changes are immediate or reversible, potential side effects (e.g., battery drain at higher speeds), or error handling. This leaves significant gaps for a mutation tool.

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 sentence that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 this is a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after setting the speed (e.g., confirmation, error responses), behavioral constraints, or how it interacts with sibling tools. For a tool that modifies device state, more context is needed.

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?

The description adds minimal value beyond the input schema, which has 100% coverage and fully documents the 'speed' parameter with enum values. The description only restates that it sets 'suction speed,' which is already implied by the tool name and schema. No additional context on parameter meaning or usage is provided.

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 ('Set') and the target resource ('suction speed of the robovac'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'robovac_get_clean_speed' or 'robovac_set_work_mode', which would require mentioning it's specifically for adjusting cleaning power versus other settings.

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., the robovac must be connected or in a certain state), exclusions (e.g., not usable while cleaning), or comparisons to siblings like 'robovac_set_work_mode' for broader mode changes.

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