Skip to main content
Glama
ecovacs-ai

Ecovacs MCP Server

Official
by ecovacs-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_work_state

Check the current cleaning or charging status of your Ecovacs robot vacuum to monitor its activity and progress.

Instructions

Query robot working status

Args: nickname: Robot nickname, used to find device

Returns: Dict: Dictionary containing robot working status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nicknameYesRobot nickname, used to find device

Implementation Reference

  • ecovacs_mcp/robot_mcp_stdio.py:91-104 (handler)
    The handler function for the 'get_work_state' tool. It is decorated with @mcp.tool() for registration and executes the API call to retrieve the robot's working state using the 'GetWorkState' command.
    @mcp.tool()
async def get_work_state(
    nickname: str = Field(description="Robot nickname, used to find device")
) -> dict:
    """
    Query robot working status
    
    Args:
        nickname: Robot nickname, used to find device
    
    Returns:
        Dict: Dictionary containing robot working status
    """
    return await call_api(ENDPOINT_ROBOT_CTL, {"nickName": nickname, "cmd": "GetWorkState", "act": ""})

Tool Definition Quality

C2.8/5.0
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. It states this is a query operation but doesn't mention whether it's read-only, requires authentication, has rate limits, or what specific status information is returned. The description provides minimal behavioral context beyond the basic operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably concise with clear sections for Args and Returns, but the 'Query robot working status' statement is somewhat vague. The structure is functional but not optimally front-loaded with the most critical 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?

For a query tool with no annotations and no output schema, the description is insufficient. It doesn't explain what specific status information is returned, what format the dictionary contains, or any error conditions. Given the complexity of querying device status, more context is needed for effective tool use.

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%, so the schema already fully documents the single 'nickname' parameter. The description repeats the parameter documentation verbatim without adding any additional meaning or context beyond what's in the schema, meeting the baseline expectation.

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 verb 'Query' and resource 'robot working status', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_device_list' which might also provide status information, preventing a perfect score.

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 like 'get_device_list' or when not to use it. The description lacks any context about prerequisites or appropriate scenarios for querying robot status.

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/ecovacs-ai/ecovacs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server