Skip to main content
Glama

Inspect Adb Display

inspect_adb_display
Idempotent

Reports a connected Android device's declared display size and density, including overridden wm size and wm density values, to diagnose screen configuration issues. Read-only.

Instructions

Report the display's physical and any overridden size (wm size) and density (wm density) as the device declares them. Read-only; setting values is not exposed.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "emulator-5554"
    },
    "name": "inspect_adb_display"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior1/5

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

The description asserts 'Read-only; setting values is not exposed', but annotations declare readOnlyHint=false. That is a direct conflict on exactly the property the annotations are meant to convey, so the agent receives contradictory safety signals. It also says nothing about what happens on an unreachable device or whether overrides may be absent.

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?

Two short sentences, front-loaded with the reported quantities and followed by the scope limit. Every clause contributes; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does its job by enumerating what is returned: physical size, any override, and density, as the device declares them. The remaining gap is the unresolved safety claim versus the annotations, plus no note on absent override values, but structurally the definition is nearly complete for a one-parameter read tool.

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?

There is a single parameter at 100% schema description coverage, so the schema already explains that `serial` must match `adb devices` output exactly. The description adds no further meaning about the parameter, which is the expected baseline when the schema carries full coverage.

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?

Names a specific verb and resource: report the display's physical size, any overridden size, and density, and it grounds these in the concrete `wm size` / `wm density` concepts. That is clearly separable from siblings like inspect_adb_window (windows) or inspect_adb_device (device metadata), though it does not name an alternative explicitly.

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 closing clause 'setting values is not exposed' implies this is the read path for display metrics, which weakly signals when to reach for it. There is no explicit when-to-use guidance, no mention of prerequisites such as an authorized/connected device, and no pointer to a sibling for adjacent display or window questions.

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

Deploy Server

Other Tools