Skip to main content
Glama

adb_location

Control Android device location services by setting the mode to off, sensors (GPS only), battery (network only), or high (GPS + network), with an optional device serial target.

Instructions

Enable or disable location services

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": {
      "mode": "<mode>"
    },
    "name": "adb_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesLocation mode: off, sensors (GPS only), battery (network only), high (GPS + network)
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

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 largely drops it. It does not say whether this mutates a persistent system setting, whether root or special permissions are required, whether running apps are affected, or what the call returns. For a device-state mutation with zero annotation coverage, that is a substantial gap.

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, which is appropriate for a simple two-parameter toggle. It is efficient but so terse that useful context was omitted rather than condensed.

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 mutation tool with no annotations and no output schema, the definition is too thin: it omits permission requirements, persistence/reversibility of the setting change, and any indication of success or failure reporting. Complexity is low, but the agent still lacks enough to invoke it confidently alongside the many sibling tools.

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 the enum already spells out off/sensors/battery/high with their GPS/network meanings, so the description has nothing left to add. It does not explain the optional 'device' serial or default-device behavior, but the schema covers it, 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 pair ('enable or disable') and resource ('location services'), so the agent knows exactly what device setting is touched. It does not distinguish itself from adjacent siblings like adb_airplane_mode, adb_gps_firmware, or adb_settings_put, which an agent could reasonably consider for the same goal.

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?

There is no when-to-use guidance, no prerequisites (root, permissions, device connectivity), and no mention of alternatives. The agent must infer that this is the right tool rather than a settings write or airplane-mode toggle.

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