Skip to main content
Glama

phone_device_info

Retrieves Android battery status, foreground app, and Agent Bridge permissions to check device state and available controls.

Instructions

Battery (level, charging, temperature, power saver, screen on), the app in front, and which permissions Agent Bridge has (system settings, Do Not Disturb, screen capture, gestures).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not state that the call is read-only, whether it can trigger OS permission prompts, or whether it has side effects. Only the implicit framing of 'info' hints at safety, which is not enough disclosure for a zero-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.

Conciseness3/5

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

It is a single compact clause with no filler, and the most concrete items (battery) come first. However, the sentence-fragment form means the reader has to supply the implied verb, which weakens front-loading of purpose.

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 no-arg, no-output-schema read tool, the enumeration of returned data partially substitutes for return documentation, which is helpful. It still omits any statement of side-effect safety, permission implications, or freshness of the data, leaving real gaps given how little structured metadata accompanies it.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The listed data categories loosely serve as a statement of what the fixed call retrieves.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text enumerates the specific data surfaced (battery level/charging/temperature, foreground app, held permissions), so the resource is identifiable, but it is a bare noun phrase with no verb — the agent must infer that this is a read/retrieval tool. It also overlaps with siblings like phone_status and phone_permissions without stating the boundary.

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 when-to-use statement, no prerequisite, and no reference to an alternative. The agent gets a content list but nothing about which situations should select this tool over phone_status or phone_permissions.

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