Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_pause

Pause the Eufy RoboVac cleaning cycle to temporarily stop vacuuming, allowing you to address obstacles or interruptions.

Instructions

Pause robovac cleaning

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the robovac_pause tool. Checks if RoboVac is initialized and calls the pause method on the RoboVac instance.
    case "robovac_pause":
      this.ensureRoboVacInitialized();
      await this.robovac!.pause();
      return {
        content: [
          {
            type: "text",
            text: "RoboVac paused!",
          },
        ],
      };
  • src/server.ts:157-164 (registration)
    Tool registration in the listTools handler, defining name, description, and empty input schema for robovac_pause.
    {
      name: "robovac_pause",
      description: "Pause robovac cleaning",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for robovac_pause tool, which requires no parameters.
    inputSchema: {
      type: "object",
      properties: {},
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action ('Pause') but doesn't disclose behavioral traits such as whether this requires the robovac to be connected or in a specific state, what happens if invoked incorrectly (e.g., error handling), or any side effects (e.g., might stop movement immediately). This leaves gaps for a mutation tool with zero annotation coverage.

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 with no wasted words. It's front-loaded with the core action and target, making it easy to scan and understand immediately. Every word earns its place by conveying essential information.

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 complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral context (e.g., state requirements, error responses) and doesn't explain what the tool returns or any side effects. This makes it inadequate for safe and effective use 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate, but it also doesn't introduce any confusion. Baseline is 4 for zero parameters, as the schema fully handles the case.

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 ('Pause') and target ('robovac cleaning'), making the purpose immediately understandable. It distinguishes from siblings like 'robovac_play' and 'robovac_stop_cleaning' by specifying the pause action. However, it doesn't explicitly differentiate from 'robovac_get_play_pause' which might be a status check, so it's not fully specific about being a command versus a query.

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. It doesn't mention prerequisites (e.g., requires the robovac to be actively cleaning), exclusions (e.g., not applicable when paused or stopped), or direct alternatives like 'robovac_play' to resume. The agent must infer usage from context 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