Skip to main content
Glama

adb_settings_get

Reads an Android settings value from system, secure, or global namespaces using namespace and key, so agents can inspect device configuration.

Instructions

Read an Android settings value from any namespace (system, secure, global)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "namespace": "<namespace>",
      "key": "<key>"
    },
    "name": "adb_settings_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesSetting key (e.g., 'screen_brightness', 'location_mode', 'airplane_mode_on')
deviceNoDevice serial
namespaceYesSettings namespace

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. Changed2 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / key / minLength
      Added value: +1
  3. First observedv1.1.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It correctly signals a read operation and namespace scope, but it does not disclose permission/root requirements, failure behavior for unknown keys, or whether the value is returned raw; those are important for an ADB settings read 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 one front-loaded sentence with no filler. Every element, the read action, the settings resource, and the namespace list, contributes directly to selecting and invoking the tool.

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-only settings getter, the description is minimally adequate: it identifies the resource and namespace scope. However, with no annotations and no output schema, it leaves permission requirements and return-value shape unstated, so the definition is not fully self-contained.

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%, so the input schema already documents the key, device, and namespace parameters, including examples for key and an enum for namespace. The description repeats the namespace scope but adds no parameter-level meaning beyond the schema, which fits the baseline of 3.

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 gives a specific verb and resource ("Read an Android settings value") and explicitly covers all three namespaces, which clearly distinguishes it from the write-oriented sibling adb_settings_put. It is not quite a 5 because it does not explicitly mention sibling alternatives such as adb_getprop 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 Guidelines2/5

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

The description implies usage by stating it reads settings values, but it gives no explicit when-to-use guidance, no exclusions, and no comparison to alternatives like adb_getprop or adb_shell. An agent must infer that this is for settings namespaces rather than system properties or arbitrary shell commands.

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