Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_get_all_statuses

Retrieve comprehensive status information from your Eufy RoboVac vacuum cleaner in a single request, including battery level, cleaning mode, and current operation state.

Instructions

Get all status information from the robovac at once

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoForce refresh of cached data

Implementation Reference

  • Handler for robovac_get_all_statuses tool: ensures RoboVac is initialized, calls getStatuses with optional force flag, returns JSON-stringified all statuses.
    case "robovac_get_all_statuses":
      this.ensureRoboVacInitialized();
      const allStatuses = await this.robovac!.getStatuses(
        args?.force as boolean
      );
      return {
        content: [
          {
            type: "text",
            text: `All RoboVac Statuses:\n${JSON.stringify(
              allStatuses,
              null,
              2
            )}`,
          },
        ],
      };
  • src/server.ts:258-271 (registration)
    Registration of the robovac_get_all_statuses tool in the listTools handler, including description and input schema with optional 'force' boolean parameter.
    {
      name: "robovac_get_all_statuses",
      description: "Get all status information from the robovac at once",
      inputSchema: {
        type: "object",
        properties: {
          force: {
            type: "boolean",
            description: "Force refresh of cached data",
            default: false,
          },
        },
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying it's a read operation, but doesn't clarify if it requires authentication, has rate limits, or what happens on failure. The phrase 'at once' hints at batch retrieval but lacks detail on response format or potential performance impacts.

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. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'all status information' includes, how it's structured, or potential errors. For a tool that aggregates data from multiple sibling tools, more context on the return format and usage scenarios is needed.

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?

The input schema has 100% description coverage, with the 'force' parameter fully documented in the schema itself. The description adds no additional meaning about parameters beyond what the schema provides, such as explaining when to use 'force' or its implications. With high schema coverage, the baseline score of 3 is appropriate.

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 ('Get all status information') and resource ('from the robovac'), making the purpose understandable. It distinguishes itself from sibling tools like 'robovac_get_status' by specifying 'all status information at once', though it doesn't explicitly contrast with other status-related tools like 'robovac_get_battery' or 'robovac_get_work_status'.

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 when it's preferable over individual status tools (e.g., 'robovac_get_battery') or the more general 'robovac_get_status', nor does it specify prerequisites like needing the robovac to be connected first.

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