Skip to main content
Glama

phone_permissions

Check and grant one-time Android permissions over USB with adb, including Modify system settings and Do Not Disturb access.

Instructions

Check what Agent Bridge is allowed to do. grant=true switches on the one-time permissions (Modify system settings, Do Not Disturb access) over USB with adb.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "phone_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
grantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden and does deliver the key behavioral fact: grant=true performs a mutation (enabling Modify system settings and Do Not Disturb access) over USB via adb. It does not say whether the grant is reversible, whether USB debugging/authorization is required first, what happens if the device is disconnected, or what the check mode returns.

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?

Two short sentences, front-loaded with the read operation and followed by the mutating flag. 'Over USB with adb' is a useful implementation hint rather than filler, though the phrase 'the one-time permissions' is slightly awkward and could be clarified.

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?

There is no output schema and no annotations, so the description should explain the return (e.g., which permissions are reported and their states), and it does not. It is reasonably complete for the mutation path but leaves the query path and the response shape underspecified.

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 0%, so the description must explain the single parameter, and it does explain what grant=true does. However it never states the behavior for grant=false or an omitted grant, which matters because the parameter is optional and the default mode determines whether a side effect occurs.

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 uses a specific verb (check) plus a concrete resource (what Agent Bridge is allowed to do) and adds a second mode (grant=true enabling one-time permissions), so an agent can distinguish it from generic settings tools like phone_settings. The only weakness is that 'Agent Bridge' and the permission scope are not fully defined for an agent unfamiliar with the platform.

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 usage: call it plainly to check status, or with grant=true to switch on the one-time permissions. It never states when to prefer this over siblings such as phone_settings or phone_toggle, and gives no prerequisites or warnings about when not to grant.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.