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

mobile-debug-mcp

by clivejefferies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_debugger_breakpoint

Set an exact source breakpoint by Android class name or iOS absolute source file plus line; unloaded classes/images stay pending and no silent line relocation.

Instructions

Set an exact source breakpoint: Android className or iOS absolute sourceFile (exactly one), plus line; unloaded classes/images remain pending. No silent line relocation.

Input Schema

NameRequiredDescriptionDefault
lineYes
classNameNo
timeoutMsNo
sourceFileNo
responseModeNodebug
debugSessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.35.0
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "sourceFile"
+      ]
+    },
+    "required": [
+      "className"
+    ]
+  },
+  {
+    "not": {
+      "required": [
+        "className"
+      ]
+    },
+    "required": [
+      "sourceFile"
+    ]
+  }
+]
    • addedInput schema / properties / responseMode
      Added value: +{
+  "default": "debug",
+  "enum": [
+    "compact",
+    "debug"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / sourceFile
      Added value: +{
+  "maxLength": 512,
+  "minLength": 1,
+  "pattern": "^\\/[^\\0\\r\\n]+$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "debugSessionId",
-  "className",
-  "line"
-]New value: +[
+  "debugSessionId",
+  "line"
+]
  2. Addedv0.34.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose two non-obvious traits: breakpoints on unloaded classes/images remain pending rather than failing, and there is no silent line relocation. It omits session-state prerequisites, duplicate-breakpoint handling, and what the timeout/response does, so it is not fully complete.

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?

One front-loaded sentence that leads with the core action and then the identifier constraint; every clause carries information. The semicolon-chained density makes it slightly harder to parse than it needs to be, but nothing is wasted.

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 mutation tool with no annotations and no output schema, the definition covers identifier selection and pending-breakpoint behavior but says nothing about required session state, duplicate handling, or what a successful response returns. Adequate to call, not adequate to predict the outcome.

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 0%, so the description must compensate; it does add platform meaning for className and sourceFile (Android vs iOS, absolute path) beyond the schema pattern, plus the line pairing. However debugSessionId, timeoutMs, and responseMode go entirely undocumented, leaving half the parameters with no semantics anywhere.

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?

States a specific verb and resource ("Set an exact source breakpoint") and immediately scopes the two identifier forms by platform (Android className vs iOS absolute sourceFile), which no sibling tool does. An agent can distinguish it from remove_debugger_breakpoint purely from the name/verb pair plus this text.

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 "exactly one" constraint implies when the tool is applicable (Android vs iOS targets), but there is no explicit when-to-use/when-not guidance, no mention of prerequisites such as an attached/paused debug session, and no named alternatives. Usage is inferable rather than stated.

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