Skip to main content
Glama

adb_get_system_info

Retrieve Android device system information including hardware and software details for debugging and management purposes.

Instructions

Get system information from the device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdNoDevice ID (optional)

Implementation Reference

  • Core handler function that runs multiple ADB shell commands to gather device system information including Android version, manufacturer, model, kernel, uptime, memory, and CPU info.
    async getSystemInfo(deviceId?: string) {
      try {
        const connected = await this.adbClient.isDeviceConnected(deviceId);
        if (!connected) {
          return {
            success: false,
            error: 'Device not connected',
            message: 'Cannot get system info - device is not connected'
          };
        }
    
        const commands = {
          androidVersion: 'getprop ro.build.version.release',
          apiLevel: 'getprop ro.build.version.sdk',
          manufacturer: 'getprop ro.product.manufacturer',
          model: 'getprop ro.product.model',
          brand: 'getprop ro.product.brand',
          device: 'getprop ro.product.device',
          buildId: 'getprop ro.build.id',
          kernel: 'uname -r',
          uptime: 'uptime',
          meminfo: 'cat /proc/meminfo | head -5',
          cpuinfo: 'cat /proc/cpuinfo | grep "model name" | head -1'
        };
    
        const systemInfo: Record<string, string> = {};
        
        for (const [key, cmd] of Object.entries(commands)) {
          const result = await this.adbClient.executeCommand(`shell ${cmd}`, deviceId);
          systemInfo[key] = result.success ? result.output.trim() : 'N/A';
        }
    
        return {
          success: true,
          data: {
            ...systemInfo,
            deviceId: deviceId || this.adbClient.getDefaultDevice()
          },
          message: 'System information retrieved successfully'
        };
      } catch (error: any) {
        return {
          success: false,
          error: error.message,
          message: 'Failed to get system info'
        };
      }
    }
  • src/index.ts:373-386 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the tool name, description, and input schema (optional deviceId).
    {
      name: 'adb_get_system_info',
      description: 'Get system information from the device',
      inputSchema: {
        type: 'object',
        properties: {
          deviceId: {
            type: 'string',
            description: 'Device ID (optional)',
          },
        },
        required: [],
      },
    },
  • Dispatch handler in the CallToolRequestSchema switch statement that invokes the ShellTools.getSystemInfo method.
    case 'adb_get_system_info':
      return await this.handleToolCall(this.shellTools.getSystemInfo(args?.deviceId as string));
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 states the action but doesn't describe what 'system information' includes, whether this requires device access or specific permissions, potential errors, or the format of the returned data. This leaves significant gaps for an agent to understand the tool's behavior beyond the basic action.

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 no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration, earning a top score for brevity and structure.

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 retrieving system information, the lack of annotations, and no output schema, the description is incomplete. It doesn't clarify what 'system information' entails, how results are structured, or any behavioral nuances, leaving the agent with insufficient context to use the tool effectively beyond its basic function.

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 'deviceId' parameter documented as optional. The description doesn't add any meaning beyond this, such as explaining when to specify the deviceId or default behaviors. Since the schema covers the parameter adequately, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 'system information from the device', making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'adb_get_device_info' or 'adb_get_battery_info', which also retrieve device information, leaving some ambiguity about what specific system information is targeted.

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 'adb_get_device_info' or 'adb_get_battery_info'. It lacks context about prerequisites, such as device connectivity or permissions, and doesn't mention any exclusions or specific scenarios where this tool is preferred over others.

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/richard0913/adb-mcp'

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