Skip to main content
Glama

adb_getprop

Retrieve a specific Android system property by key, or list all system properties when no key is provided. Use it to inspect build details, device settings, and runtime configuration via ADB.

Instructions

Get a specific Android system property, or all properties if no key given

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adb_getprop"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoProperty key (e.g., 'ro.build.version.sdk'). Omit for all.
deviceNoDevice serial

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; 'Get' implies a non-mutating read, and the no-key dump behavior is explicit. It does not confirm read-only behavior or describe the output shape and potentially large result when retrieving all properties.

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?

A single front-loaded sentence communicates both operating modes without filler or redundancy. Its brevity is appropriate for this simple getter.

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

Completeness4/5

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

For a simple two-parameter getter with fully documented inputs, the description supplies enough information to understand and invoke the core operation. Return format and default-device behavior remain undocumented, which matters slightly more because there is no output schema.

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?

Schema description coverage is 100%, including an example property key and the instruction to omit it for all properties, so the baseline is 3. The description reinforces the optional-key behavior but adds no detail about device serial selection or the default when device is omitted.

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 and resource: getting an Android system property, with the useful distinction that omitting the key retrieves all properties. It does not differentiate the tool from siblings such as adb_settings_get or adb_shell.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The Android-system-property scope and optional all-properties mode provide clear usage context. There are no exclusions or alternative-tool recommendations, such as using adb_settings_get for Android settings rather than system properties.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools