Skip to main content
Glama
charlesmuchene

Android Preference Editor MCP Server

devices

List connected Android devices to identify targets for preference editing during app development.

Instructions

Lists connected Android devices

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'devices' tool. It asynchronously lists connected Android devices using the imported listDevices function, maps each device's serial to a text content block, and handles errors by returning an error message.
    server.tool("devices", "Lists connected Android devices", async () => {
      try {
        return {
          content: (await listDevices()).map((device) => ({
            type: "text",
            text: device.serial,
          })),
        };
      } catch (error) {
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: error instanceof Error ? error.message : "Unknown error",
            },
          ],
        };
      }
    });
  • The 'devices' tool is registered here within the configureCommonTools function using server.tool(). This registration includes the description and the inline handler.
    server.tool("devices", "Lists connected Android devices", async () => {
      try {
        return {
          content: (await listDevices()).map((device) => ({
            type: "text",
            text: device.serial,
          })),
        };
      } catch (error) {
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: error instanceof Error ? error.message : "Unknown error",
            },
          ],
        };
      }
    });
  • DeviceSchema defines the input structure for tools that interact with a specific Android device, using deviceId (serial number), which is relevant to the 'devices' tool that lists such serials.
    export const DeviceSchema = z.object({
      deviceId: z.string().describe("The device's serial number."),
    });
  • src/index.ts:21-22 (registration)
    configureCommonTools(server) is called here, which in turn registers the 'devices' tool.
    configurePreferenceTools(server);
    configureCommonTools(server);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the listing function without mentioning whether this requires permissions, how results are returned (e.g., format, pagination), or any limitations (e.g., only shows currently active devices). This leaves significant gaps in understanding the tool's 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, efficient sentence that directly states the tool's purpose with no wasted words. It is front-loaded and appropriately sized for a simple listing tool, making it easy to parse quickly.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It lacks details on behavioral aspects like return format or usage context, which are important even for simple tools. However, it meets the basic requirement of stating what the tool does.

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 the input schema has 100% description coverage (though empty). The description doesn't need to explain parameters, so it appropriately avoids this. A baseline of 4 is applied for zero-parameter tools, as there's nothing to compensate for.

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 ('Lists') and the resource ('connected Android devices'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_apps' or 'list_files' beyond the resource type, which prevents 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?

The description provides no guidance on when to use this tool versus alternatives like 'list_apps' or 'list_files', nor does it mention any prerequisites or context for usage. It merely states what the tool does without indicating appropriate scenarios.

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/charlesmuchene/pref-editor-mcp-server'

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