Skip to main content
Glama

phone_settings

Opens Android system settings pages directly, including Wi-Fi, Bluetooth, battery, privacy, and app info, to reach the exact configuration screen without manual navigation.

Instructions

Open a system settings page directly: settings, wifi, bluetooth, mobile-data, airplane, hotspot, nfc, location, display, sound, battery, storage, apps, notifications, security, privacy, accessibility, date, language, keyboard, developer, about, dnd, cast, vpn; Android 10+ panels: wifi-panel, internet-panel, volume-panel. Or app= for an app's info page (permissions, storage, force stop).

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_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNo
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does communicate that this navigates the device UI to a settings screen (a state-changing navigation). It says nothing about what happens with an unrecognized page value, whether the device must be unlocked, or whether it merely navigates versus returning any data, which are real gaps for a no-annotation tool.

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?

The action is front-loaded in a single opening clause, and the long value list is dense but earns its space as the only enum documentation available. Grouping is loosely flagged by the 'Android 10+ panels' and 'Or app=' markers, though the bare list is harder to scan than it could be.

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?

For a two-optional-parameter tool with no annotations and no output schema, the description covers the input vocabulary well but omits precedence between `app` and `page`, the no-argument behavior, and any notion of failure or return. These are modest but real gaps for an agent that must call it reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description has to define both parameters from scratch, and it largely does: it enumerates the accepted `page` values (including the Android 10+ panel variants) and explains `app` takes a package name for an app's info page. It does not state whether `app` and `page` are mutually exclusive or what the default page is when neither is supplied.

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 ('Open a system settings page directly') and then enumerates every valid page plus the alternate app=<package> mode, so the agent knows exactly what the tool does. The app-info-page mode implicitly separates it from phone_open_app, which launches an app rather than its settings screen.

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

Usage Guidelines4/5

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

The word 'directly' signals this is the shortcut route rather than navigating through taps (phone_tap/phone_swipe), and the 'Or app=<package>' clause tells the agent which input form to pick for app-level settings. There are no explicit exclusions or named alternatives for edge cases such as toggling a radio, so it stops short of a 5.

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