Eufy RoboVac MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| robovac_set_work_modeC | Set the cleaning mode of the robovac |
| robovac_set_clean_speedC | Set the suction speed of the robovac |
| robovac_playB | Start/resume robovac cleaning |
| robovac_pauseB | Pause robovac cleaning |
| robovac_find_robotB | Make the robovac beep to help locate it |
| robovac_get_error_codeC | Get the current error code of the robovac |
| robovac_get_work_modeC | Get the current work mode of the robovac |
| robovac_get_clean_speedB | Get the current cleaning speed of the robovac |
| robovac_get_work_statusC | Get the current work status of the robovac |
| robovac_get_play_pauseB | Get the current play/pause state of the robovac |
| robovac_format_statusB | Get a formatted display of all robovac status information |
| robovac_get_all_statusesC | Get all status information from the robovac at once |
| robovac_auto_initializeC | Automatically discover and initialize the first RoboVac device found |
| robovac_connect_discoveredC | Connect to a discovered RoboVac device by IP (requires device ID and local key) |
| robovac_connectB | Connect to your RoboVac using device credentials (manual setup) |
| robovac_start_cleaningB | Start the robovac cleaning cycle |
| robovac_stop_cleaningB | Stop the robovac cleaning cycle |
| robovac_return_homeA | Send the robovac back to its charging dock |
| robovac_get_statusB | Get the current status of the robovac |
| robovac_get_batteryA | Get the battery level of the robovac |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Multiple tools have unclear boundaries and overlapping purposes, causing potential confusion. For example, robovac_play and robovac_start_cleaning both seem to initiate cleaning, while robovac_get_status, robovac_get_all_statuses, and robovac_format_status all retrieve status information with unclear distinctions. The descriptions don't sufficiently differentiate these tools, making it hard for an agent to choose correctly.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case with clear prefixes like 'robovac_' for all tools. The naming convention is predictable and readable, with no deviations or mixed styles, making it easy to understand the purpose of each tool at a glance.
With 20 tools, this server feels overly heavy and redundant for controlling a RoboVac. Many tools could be consolidated (e.g., multiple status getters or cleaning controls), leading to unnecessary complexity. A more streamlined set of 5-10 tools would better suit the domain without sacrificing functionality.
The tool surface covers the core RoboVac operations well, including connection, status retrieval, cleaning control, and settings adjustment. Minor gaps exist, such as lack of scheduling or zone cleaning tools, but agents can work around these with the available tools. The coverage is sufficient for basic to intermediate use cases.