Skip to main content
Glama
appleton

Eufy RoboVac MCP Server

by appleton

robovac_get_battery

Check the battery level of your Eufy RoboVac to monitor cleaning readiness and plan charging cycles.

Instructions

Get the battery level of the robovac

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the robovac_get_battery tool. Ensures the RoboVac is initialized and calls getBatteyLevel() on the robovac instance to retrieve the battery level, then returns it as a text response.
    case "robovac_get_battery":
      this.ensureRoboVacInitialized();
      const battery = await this.robovac!.getBatteyLevel();
      return {
        content: [
          {
            type: "text",
            text: `Battery Level: ${battery}%`,
          },
        ],
      };
  • src/server.ts:377-383 (registration)
    Tool registration in the MCP server's tools list, including the name, description, and empty input schema.
      name: "robovac_get_battery",
      description: "Get the battery level of the robovac",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema definition for the robovac_get_battery tool, which expects no parameters (empty object).
    inputSchema: {
      type: "object",
      properties: {},
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read-only operation ('Get'), but doesn't disclose potential side effects, error conditions, authentication needs, or rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose and efficiently communicates what the tool does without any structural fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read operation with no parameters and no output schema, the description is minimally adequate. However, without annotations or output schema, it doesn't explain what format the battery level returns (e.g., percentage, voltage) or potential error responses, leaving some contextual gaps.

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 with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, maintaining focus on the tool's purpose without unnecessary detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get') and resource ('battery level of the robovac'), making the purpose immediately understandable. It distinguishes itself from siblings like 'robovac_get_status' or 'robovac_get_all_statuses' by focusing exclusively on battery information.

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 prerequisites (e.g., whether the robovac must be connected first), nor does it clarify if battery level is included in other status tools, leaving the agent to infer usage context.

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