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

mobile-debug-mcp

by clivejefferies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_system_trace_capabilities

Checks Android Perfetto or iOS Instruments profiling prerequisites without recording, including required iOS booted simulator device ID, template options, and unknown permissions.

Instructions

Probe Android Perfetto or iOS Instruments prerequisites without recording. iOS requires explicit booted simulator deviceId; reports template matrix and unknown profiling permissions.

Input Schema

NameRequiredDescriptionDefault
appIdNoiOS only: running development app bundle identifier; required for iOS start.
deviceIdNo
platformYes
templateNoiOS only. Default Time Profiler; initial simulator support is Time Profiler only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.35.0
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "not": {
+      "anyOf": [
+        {
+          "required": [
+            "appId"
+          ]
+        },
+        {
+          "required": [
+            "template"
+          ]
+        }
+      ]
+    },
+    "properties": {
+      "platform": {
+        "const": "android"
+      }
+    }
+  },
+  {
+    "properties": {
+      "platform": {
+        "const": "ios"
+      }
+    },
+    "required": [
+      "deviceId"
+    ]
+  }
+]
    • addedInput schema / properties / appId
      Added value: +{
+  "description": "iOS only: running development app bundle identifier; required for iOS start.",
+  "minLength": 1,
+  "pattern": "^[a-zA-Z0-9._-]+$",
+  "type": "string"
+}
    • addedInput schema / properties / template
      Added value: +{
+  "description": "iOS only. Default Time Profiler; initial simulator support is Time Profiler only.",
+  "enum": [
+    "System Trace",
+    "Time Profiler",
+    "Animation Hitches",
+    "Hangs"
+  ],
+  "type": "string"
+}
  2. Addedv0.34.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key traits: the probe has no recording side effect, iOS demands a booted simulator deviceId, and permission results may come back unknown. It leaves out failure behavior, whether it touches device state, and what 'unknown profiling permissions' means operationally for the caller.

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?

Two tight sentences with the platform scope and the no-recording constraint front-loaded. The telegraphic style ('reports template matrix and unknown profiling permissions') trades a little clarity for density but wastes no words.

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?

For a four-parameter probe with no annotations and no output schema, the description covers scope, platform asymmetry, the iOS prerequisite, and roughly what is returned. Remaining gaps — the android-side prohibition on appId/template and the purpose of expectedState — are edges an agent can likely infer from the schema.

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%, and the description compensates for the undocumented deviceId by specifying 'explicit booted simulator deviceId' for iOS, which the schema does not say. It says nothing about appId's platform-restricted, optional nature here, and the 'template matrix' phrase only loosely ties to the template enum.

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

Purpose5/5

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

Names a specific verb and resource ('Probe ... prerequisites') and scopes it to the two profiling backends (Android Perfetto, iOS Instruments). The clause 'without recording' distinguishes it from the recording-oriented siblings start_system_trace and stop_system_trace without the agent needing to open any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'without recording' clearly frames this as a pre-flight check to run before starting a trace, which is actionable context. It stops short of naming start_system_trace as the follow-up alternative or stating exclusions, so the routing is implied rather than explicit.

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