Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_stop_cleaning

Stop the Eufy RoboVac cleaning cycle to pause or end vacuuming sessions when needed.

Instructions

Stop the robovac cleaning cycle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'robovac_stop_cleaning' tool. It ensures the RoboVac is initialized and calls pause() on the RoboVac instance to stop cleaning.
    case "robovac_stop_cleaning":
      this.ensureRoboVacInitialized();
      await this.robovac!.pause();
      return {
        content: [
          {
            type: "text",
            text: "RoboVac cleaning stopped!",
          },
        ],
      };
  • src/server.ts:352-359 (registration)
    Registration of the 'robovac_stop_cleaning' tool in the listTools response, including name, description, and empty input schema.
    {
      name: "robovac_stop_cleaning",
      description: "Stop the robovac cleaning cycle",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for the 'robovac_stop_cleaning' tool, which requires 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 but offers minimal behavioral insight. It states what the tool does but doesn't disclose effects like whether the robovac remains in place, returns to dock, or retains cleaning progress. For a control tool with zero annotation coverage, this is inadequate.

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, direct sentence with zero wasted words. It's front-loaded with the core action and target, making it highly efficient and easy to parse.

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?

For a control tool with no annotations and no output schema, the description is too sparse. It doesn't explain what happens after stopping (e.g., does the robovac pause, return home, or shut down?) or potential side effects, leaving significant gaps for an agent to understand the tool's behavior.

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 zero parameters with 100% schema coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, earning a high baseline score for not introducing unnecessary complexity.

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 ('Stop') and target ('robovac cleaning cycle'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'robovac_pause' or 'robovac_return_home', 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?

The description provides no guidance on when to use this tool versus alternatives like 'robovac_pause' or 'robovac_return_home'. It lacks context about whether this stops cleaning permanently versus temporarily, or if it should be used during active cleaning only.

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