Ecovacs MCP Server
OfficialServer 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 |
|---|---|
| set_cleaningC | Start robot cleaning Args: nickname: Robot nickname, used to find device act: Cleaning action s-start cleaning, r-resume cleaning, p-pause cleaning, h-stop cleaning Returns: Dict: Dictionary containing execution results |
| set_chargingB | Make robot return to charging station Args: nickname: Robot nickname, used to find device act: Robot action, go-start begin returning to charging station, stopGo stop returning to charging station Returns: Dict: Dictionary containing execution results |
| get_work_stateC | Query robot working status Args: nickname: Robot nickname, used to find device Returns: Dict: Dictionary containing robot working status |
| get_device_listC | Query robot list Returns: Dict: Dictionary containing list of robot nicknames |
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 4 tools
Each tool has a clearly distinct purpose: get_device_list retrieves robot information, get_work_state queries status, set_charging controls charging behavior, and set_cleaning manages cleaning operations. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern with clear, descriptive names: get_device_list, get_work_state, set_charging, and set_cleaning. The naming convention is uniform throughout the set.
With 4 tools, the count is reasonable for a robot vacuum control server, covering core operations like listing devices, checking status, and controlling charging and cleaning. It is slightly thin but functional for basic control.
The tools cover essential operations for robot vacuum control, but there are notable gaps such as missing update/delete functions for device management, scheduling capabilities, or advanced settings like cleaning modes. The surface is functional but not fully comprehensive.