Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_return_home

Send your Eufy RoboVac back to its charging dock to recharge after cleaning sessions.

Instructions

Send the robovac back to its charging dock

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the robovac_return_home tool. Ensures RoboVac is initialized and calls goHome() method on the RoboVac instance, returning a success message.
    case "robovac_return_home":
      this.ensureRoboVacInitialized();
      await this.robovac!.goHome();
      return {
        content: [
          {
            type: "text",
            text: "RoboVac returning to charging dock!",
          },
        ],
      };
  • src/server.ts:360-367 (registration)
    Tool registration in the ListTools response, defining name, description, and empty input schema.
    {
      name: "robovac_return_home",
      description: "Send the robovac back to its charging dock",
      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 only states the action without disclosing behavioral traits. It doesn't mention whether this command requires the robovac to be powered on, connected, or in a certain mode; what happens if the dock is unreachable; whether cleaning stops automatically; or any error conditions. For a command tool with zero annotation coverage, this leaves significant behavioral gaps.

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 zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and efficient. Every word earns its place by conveying essential purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no parameters, no output schema) and lack of annotations, the description is minimally adequate but incomplete. It states what the tool does but omits important context like prerequisites, side effects, or error handling. For a command that likely interacts with hardware, more behavioral detail would improve completeness.

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, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to compensate for any parameter gaps, and it appropriately doesn't discuss nonexistent parameters. A baseline of 4 is appropriate as the description doesn't add param info but doesn't need to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Send back') and target resource ('robovac to its charging dock'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'robovac_start_cleaning' or 'robovac_pause' by focusing on navigation to the charging dock rather than cleaning operations or status queries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when the robovac needs to return to charge, but provides no explicit guidance on when to use this versus alternatives like 'robovac_stop_cleaning' or 'robovac_pause', nor any prerequisites (e.g., whether the robovac must be connected or in a certain state). Usage is contextually implied but not explicitly defined.

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