Skip to main content
Glama

adb_grant_permission

Grants a specified Android runtime permission to a package on a connected device via ADB, enabling app features that require user-approved permissions.

Instructions

Grant a runtime permission to a package

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": {
      "packageName": "<packageName>",
      "permission": "<permission>"
    },
    "name": "adb_grant_permission"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
permissionYesFull permission string (e.g., 'android.permission.READ_PHONE_STATE')
packageNameYesPackage name (e.g., 'com.example.app')

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
    • changedInput schema / properties / packageName / description
      Previous value: -"Package name"New value: +"Package name (e.g., 'com.example.app')"
  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, yet it discloses nothing about side effects, required privileges (root/shell), whether the grant persists across reboots, or what happens on failure for an undeclared permission. The phrase 'runtime permission' adds a small hint about Android permission classes, but that is the only behavioral signal.

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 clause with zero filler and no repetition of the tool name. It is efficient, though the extreme terseness leaves no room for the operational caveats this mutation tool needs.

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?

The parameters are fully covered by the schema and there is no output schema to explain, so the definition is minimally complete for invocation. However, for an unannotated destructive-adjacent mutation tool it omits prerequisites and failure behavior that an agent would need to call it safely and correctly.

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 schema already documents all three parameters including the full permission string format and package name examples. The description adds no extra meaning such as device-selection behavior when 'device' is omitted, so the baseline of 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?

The description states a specific verb ('Grant') and resource ('runtime permission') applied to a target ('a package'), so an agent immediately knows this is a permission-mutation tool. It does not, however, name or distinguish itself from close siblings such as adb_revoke_permission, adb_list_permissions, or adb_permission_audit.

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 guidance on when to use this instead of adb_revoke_permission, adb_list_permissions, or adb_shell with pm grant, and no prerequisites are stated (app must be installed, permission must be declared in the manifest, Android 6+ runtime semantics, possible root requirement). The agent must infer all selection context.

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