Skip to main content
Glama

Read Adb Setting

read_adb_setting
Idempotent

Read a single Android settings value from the system, secure, or global namespace by device serial and key; missing keys return null, and no write access is provided.

Instructions

Read one settings value (settings get) from the system, secure, or global namespace. Absent keys report the device's own null observation. Read-only; writing settings is not exposed.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "adb_enabled",
      "serial": "emulator-5554",
      "namespace": "secure"
    },
    "name": "read_adb_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesSetting key to read
serialYesDevice serial exactly as `adb devices` reports it
namespaceYesSettings namespace to read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior1/5

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

The description asserts 'Read-only; writing settings is not exposed,' while the annotations declare readOnlyHint=false, directly contradicting the stated safety profile. The useful extra detail about absent keys returning the device's own null observation is outweighed by this inconsistency.

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?

Three short sentences, front-loaded with the verb and resource, then the null-result behavior, then the write exclusion. No filler or redundant restatement of the name.

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 three-parameter read tool with a fully described schema and no output schema, the description covers scope and the null-result return behavior, which is what an agent most needs. Its remaining defect is the conflicting read-only claim rather than missing call information.

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% and all three required parameters are documented in the schema, so baseline 3 applies. The description restates the namespace enum values but adds no syntax, format, or edge-case detail for serial or key beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read one settings value (`settings get`)') and names the exact scope (system, secure, or global namespace), which no sibling tool covers. An agent can distinguish this from logcat, package, or device-inspection siblings without opening the schema.

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

Usage Guidelines3/5

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

The description implies when to use it (retrieving a single setting value by namespace and key) and rules out writing, but never states prerequisites such as a connected/authorized device or when to prefer a broader inspection sibling. Usage is inferable rather than explicit.

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