Skip to main content
Glama

phone_toggle

Toggle Android phone settings—flashlight, screen rotation, Do Not Disturb, and ringer modes—to control device behavior remotely.

Instructions

Quick device switches. flashlight: on|off. rotation: get|auto|portrait|landscape (needs "Modify system settings" once). dnd (Do Not Disturb): get|on|alarms|total|off (needs DND access once). ringer: get|normal|vibrate|silent.

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": {
      "setting": "<setting>"
    },
    "name": "phone_toggle"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNo
settingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose two real behavioral facts: rotation requires the "Modify system settings" permission once, and dnd requires DND access once. It also implicitly reveals that some values are reads (rotation: get, dnd: get, ringer: get) while others mutate state, but it never states what happens on permission failure, whether writes are idempotent, or what a "get" 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?

Four dense lines, each pairing a setting with its valid values, followed by prerequisites inline in parentheses — highly scannable and front-loaded with zero filler. The opener "Quick device switches" is thin, but it costs almost nothing and the enumeration immediately does the real work.

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 2-parameter, enum-driven tool this is close to sufficient: the agent knows the four settings, the accepted value strings, and the two one-time permission prerequisites. The notable gaps are the absence of an output schema combined with no description of what the "get" variants return, and no statement of error or failure behavior when the required permissions have not been granted.

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 description coverage is 0% and the `value` parameter is an unconstrained free string, so the per-setting value enumeration (on|off, get|auto|portrait|landscape, get|on|alarms|total|off, get|normal|vibrate|silent) is essential information found nowhere in the schema. The only shortfall is that it does not say whether `value` should be omitted for read calls, which the schema implies is not allowed since only `setting` is required.

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 opens with a specific resource class (device switches) and enumerates exactly which four settings are covered (flashlight, rotation, dnd, ringer), so the agent can tell it apart from phone_brightness or phone_volume by omission rather than by stated contrast. The verb is only loosely stated as "switches" rather than an explicit get/set, but the value lists make the read/write nature clear.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative (e.g., it never says to use phone_brightness for brightness instead). The only contextual cues are the inline prerequisites for rotation and dnd, which describe setup requirements rather than tool selection.

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