Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_format_status

Retrieve and display formatted status information for Eufy RoboVac vacuum cleaners, showing current cleaning state, battery level, and operational details.

Instructions

Get a formatted display of all robovac status information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'robovac_format_status' tool. It ensures the RoboVac instance is initialized, calls the formatStatus() method on the RoboVac object to print formatted status to console, and returns a text response instructing to use another tool for structured data.
    case "robovac_format_status":
      this.ensureRoboVacInitialized();
      await this.robovac!.formatStatus();
      return {
        content: [
          {
            type: "text",
            text: "Status information has been printed to console. Use robovac_get_all_statuses for structured data.",
          },
        ],
      };
  • src/server.ts:249-257 (registration)
    Registration of the 'robovac_format_status' tool in the list of available tools, including its name, description, and empty input schema (no parameters required).
    {
      name: "robovac_format_status",
      description:
        "Get a formatted display of all robovac status information",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema definition for the 'robovac_format_status' tool: an empty object (no required parameters).
    {
      name: "robovac_format_status",
      description:
        "Get a formatted display of all robovac status information",
      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 mentions 'formatted display' but doesn't disclose behavioral traits like whether this is a read-only operation, requires connectivity, has rate limits, or what the output format looks like (e.g., JSON, text). This leaves significant gaps for an agent to understand how to handle the tool.

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 is front-loaded and appropriately sized for a simple tool, with no wasted 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?

Given the tool's complexity (simple read operation) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'formatted' means, the return type, or any behavioral context, making it insufficient for an agent to fully understand how to use it effectively.

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% (empty schema). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for no parameters, as it doesn't introduce confusion or redundancy.

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 'formatted display of all robovac status information', making the purpose understandable. It distinguishes from siblings like robovac_get_status (singular) and robovac_get_all_statuses (unformatted), though not explicitly named. However, it could be more specific about what 'formatted' entails versus raw data.

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 robovac_get_all_statuses or other status-related siblings. The description implies a formatted output but doesn't specify contexts where this is preferred, such as for human-readable displays versus programmatic processing.

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