Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_get_status

Check the current operational status of your Eufy RoboVac vacuum cleaner to monitor its cleaning activity or connection state.

Instructions

Get the current status of the robovac

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'robovac_get_status' MCP tool. It ensures the RoboVac instance is initialized, calls getStatuses() on the library instance, and returns the status as a formatted JSON string.
    case "robovac_get_status":
      this.ensureRoboVacInitialized();
      const status = await this.robovac!.getStatuses();
      return {
        content: [
          {
            type: "text",
            text: `RoboVac Status:\n${JSON.stringify(status, null, 2)}`,
          },
        ],
      };
  • src/server.ts:368-375 (registration)
    Registration of the 'robovac_get_status' tool in the listTools handler, including name, description, and empty input schema.
    {
      name: "robovac_get_status",
      description: "Get the current status of the robovac",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema definition for the 'robovac_get_status' tool (empty object, no parameters required).
    {
      name: "robovac_get_status",
      description: "Get the current status of the robovac",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but lacks behavioral details: it doesn't specify if this requires connectivity, what status information is included (e.g., battery, mode), or potential errors. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operation.

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, direct sentence with no wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse for an AI agent.

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?

Given the complexity of a status-checking tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'status' entails (e.g., operational state, battery level, errors) or the return format, leaving the agent uncertain about the tool's output and behavior.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't mention parameters, which is appropriate, earning a baseline score of 4 for adequately handling the parameter-free context.

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 ('Get') and resource ('current status of the robovac'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'robovac_get_all_statuses' or 'robovac_format_status', which would require more specificity about scope or output format.

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 about when to use this tool versus alternatives. With multiple status-related siblings (e.g., 'robovac_get_all_statuses', 'robovac_get_battery', 'robovac_get_work_status'), the description offers no context on selection criteria, leaving the agent to infer based on tool names alone.

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