Skip to main content
Glama

adb_settings_put

Write a key/value Android settings entry to the system, secure, or global namespace via ADB to configure device behavior or preferences.

Instructions

Write an Android settings value to 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>",
      "value": "<value>"
    },
    "name": "adb_settings_put"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesSetting key (e.g., 'screen_brightness' for system namespace, 'wifi_on' or 'airplane_mode_on' for global, 'location_providers_allowed' for secure). Use `adb_shell` with `settings list <namespace>` to enumerate available keys for a device.
valueYesValue to write. Type depends on the key — typically a string, integer, or 0/1 for booleans. The setting framework accepts everything as a string and parses on read.
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. Changed4 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / key / description
      Previous value: -"Setting key"New value: +"Setting key (e.g., 'screen_brightness' for system namespace, 'wifi_on' or 'airplane_mode_on' for global, 'location_providers_allowed' for secure). Use `adb_shell` with `settings list <namespace>` to enumerate available keys for a device."
    • addedInput schema / properties / key / minLength
      Added value: +1
    • changedInput schema / properties / value / description
      Previous value: -"Value to set"New value: +"Value to write. Type depends on the key — typically a string, integer, or 0/1 for booleans. The setting framework accepts everything as a string and parses on read."
  3. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it only implies mutation via 'Write'. It does not disclose that secure/global namespaces typically require elevated privileges (e.g. WRITE_SECURE_SETTINGS or root), whether the change takes effect immediately or needs a reboot/broadcast, or any warning that mis-set keys can destabilize the device.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler and the scope stated up front. It is efficient, though its brevity leaves behavioral gaps that a second sentence could have filled.

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?

For a three-required-parameter mutation tool with no annotations and no output schema, the description should explain privileges needed, effect timing, and failure behavior. None of that is present, so an agent knows what to write but not what constraints or side effects to expect.

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%, with key examples and value type guidance already documented per-parameter, so the schema does the heavy lifting. The description only restates the namespace enum values, adding no semantics beyond structured data, so the baseline 3 applies.

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?

States a specific verb ('Write') and resource ('Android settings value') plus the scope ('any namespace (system, secure, global)'), which distinguishes it from adb_settings_get and from adb_shell. It does not name the sibling it is the counterpart of, but the read/write split is inferable from the verb.

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 offers no when-to-use, when-not-to-use, or alternative guidance. The one useful pointer about enumerating keys with adb_shell lives in the input schema, not the description, and there is no mention of when to prefer adb_shell settings put over this tool.

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