Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_find_robot

Activate audible beeping on your Eufy RoboVac to locate it when lost or misplaced.

Instructions

Make the robovac beep to help locate it

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enableNoWhether to enable or disable find robot mode

Implementation Reference

  • Handler implementation for the robovac_find_robot tool. Ensures the RoboVac is connected, sets the find robot mode using the library's setFindRobot method with optional enable parameter (defaults to true), and returns a textual confirmation.
    case "robovac_find_robot":
      this.ensureRoboVacInitialized();
      const enableFind =
        args?.enable !== undefined ? (args?.enable as boolean) : true;
      await this.robovac!.setFindRobot(enableFind);
      return {
        content: [
          {
            type: "text",
            text: enableFind
              ? "Find robot enabled - RoboVac should be beeping!"
              : "Find robot disabled",
          },
        ],
      };
  • src/server.ts:165-178 (registration)
    Tool registration in the ListTools handler, defining the name, description, and input schema (object with optional boolean 'enable' property defaulting to true).
    {
      name: "robovac_find_robot",
      description: "Make the robovac beep to help locate it",
      inputSchema: {
        type: "object",
        properties: {
          enable: {
            type: "boolean",
            description: "Whether to enable or disable find robot mode",
            default: true,
          },
        },
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Make the robovac beep' implies an action that produces sound, it doesn't describe what happens (e.g., how long it beeps, whether it interrupts current operations, if it requires specific robot states, or what happens on failure). This leaves significant behavioral gaps for a tool that triggers a physical action.

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 unnecessary words. Every element ('Make the robovac beep' and 'to help locate it') contributes essential information, making it appropriately concise and well-structured.

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?

For a single-parameter tool with 100% schema coverage but no annotations or output schema, the description provides basic purpose but lacks important context. It doesn't address behavioral aspects like what the beep sounds like, duration, or error conditions, which would be valuable for an agent invoking this physical action tool.

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?

Schema description coverage is 100%, with the single parameter 'enable' clearly documented in the schema as controlling whether to enable or disable find robot mode. The description doesn't add any parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage.

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 ('Make the robovac beep') and purpose ('to help locate it'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'robovac_get_status' or 'robovac_get_all_statuses' which might also help locate the robot through status information rather than audible beeping.

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., whether the robot needs to be connected or powered on), nor does it suggest when other tools like status-checking siblings might be more appropriate for location purposes.

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