Skip to main content
Glama

phone_brightness

Read or set an Android screen’s brightness level (0–100, auto, or manual); grant Modify system settings permission once to enable changes.

Instructions

Read or set screen brightness: "get", 0–100, "auto" or "manual". Needs "Modify system settings" once (phone_permissions grant=true over USB, or the phone opens that settings page).

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

Input Schema

NameRequiredDescriptionDefault
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and usefully discloses the one-time 'Modify system settings' requirement and the two permission-grant paths. It still omits failure behavior when permission is missing, persistence semantics, and what '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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact, front-loaded sentence that moves from purpose to accepted values to prerequisite. Every clause adds information, and there is no filler.

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 simple one-parameter tool, it covers purpose, value domain, and the important permission prerequisite. Completeness is reduced because there is no output schema and the description does not explain the return value for 'get' or default behavior when value is omitted.

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%, so the description must compensate, and it does by defining the sole parameter's accepted forms: 'get', 0-100, 'auto', and 'manual'. It leaves some ambiguity about what happens when the parameter is omitted and the exact numeric format, but the core value domain is explained.

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 and resource: read or set screen brightness. It is clear without opening the schema, though it does not explicitly differentiate itself from related tools such as phone_settings or phone_toggle.

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?

It gives the accepted usage modes and value forms, plus the permission prerequisite. However, it does not explicitly say when to use this tool versus alternatives or when not to use it.

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