Skip to main content
Glama
Sign In
mobile-debug-mcp

mobile-debug-mcp

by clivejefferies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_devices

Discover connected Android devices and iOS simulators, and optionally check whether a given appId is installed on each target.

Instructions

List Android devices and iOS simulators. Supply appId for device-specific installation status; unknown checks do not imply absence.

Input Schema

NameRequiredDescriptionDefault
appIdNoOptional package or bundle identifier to check on each device.
platformNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.36.0
    • addedInput schema / properties / appId
      Added value: +{
+  "description": "Optional package or bundle identifier to check on each device.",
+  "pattern": "^[A-Za-z0-9_-]+(\\.[A-Za-z0-9_-]+)*$",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.34.0
    • addedInput schema / allOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "expectedState"
+      ]
+    }
+  }
+]
  3. First observedv0.31.0

TDQS

A3.5/5.0
Behavior3/5

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

With zero annotations, the description carries the full burden and does add real behavioral value: it discloses that appId yields per-device installation status and warns that 'unknown checks do not imply absence' — a meaningful caveat about ambiguous results. However, it says nothing about permissions, cost/latency, or what fields a device entry contains, and no output schema exists to cover that gap.

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 core action, then the parameter effect and its caveat. No filler or restatement of the tool name.

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-parameter read tool this covers the essentials, but with no annotations and no output schema, the agent is left without any picture of the returned device records or the result of an appId check. The platform parameter's role is also not spelled out, leaving modest gaps relative to the disclosure burden.

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?

Schema coverage is 50%: appId is documented in the schema, and the description adds the consequential meaning (it triggers an installation-status check per device). The platform parameter appears only obliquely, via 'Android devices and iOS simulators', so its filtering effect is inferred from the enum rather than 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?

Uses a specific verb plus resource — 'List Android devices and iOS simulators' — which also scopes the tool (Android devices, iOS simulators only). This is unambiguous and no sibling tool competes as a device-enumeration alternative, though the description does not explicitly say so. Slightly short of 5 because the scope nuance (real iOS devices vs simulators) is left implicit.

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?

Usage is implied rather than stated: 'Supply appId for device-specific installation status' tells the agent when the optional parameter matters, but there is no explicit when-to-use/when-not framing and no named alternative among the many sibling device/app tools. Adequate for a simple enumeration call but leaves selection reasoning to inference.

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