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

mobile-debug-mcp

by clivejefferies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

build_app

Build Android or iOS projects and return the artifact path without installing. Provide platform and project type to guide build tool selection.

Instructions

Build a project for Android or iOS and return the built artifact path. Does not install. platform and projectType are required.

Input Schema

NameRequiredDescriptionDefault
variantNoOptional build variant (e.g., Debug/Release)
platformYesPlatform to build for (required).
projectPathYesPath to project directory (contains gradlew or xcodeproj/xcworkspace)
projectTypeYesProject type to guide build tool selection (required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.34.0
    • addedInput schema / allOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "expectedState"
+      ]
+    }
+  }
+]
  2. First observedv0.31.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses two traits beyond the schema: the operation is non-installing and it returns an artifact path. However, for a potentially long-running build it says nothing about duration, failure modes, environment prerequisites, or whether the build is blocking.

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?

Three short, front-loaded sentences with the core action first and the constraint second. The trailing 'platform and projectType are required' duplicates the schema's required list and is the one sentence that doesn't earn its place.

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 correctly compensates by stating the return value is a built artifact path. Combined with 100% schema coverage that covers most of what an agent needs, though build prerequisites and expected runtime/failure behavior remain unstated.

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 description coverage is 100%, so every parameter is already documented including the platform/projectType enums and the gradlew/xcodeproj hint for projectPath. The description only repeats that platform and projectType are required (already in the `required` array) and adds nothing about `variant` or path expectations, so baseline 3 applies.

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 (build a project) and narrows the scope to Android/iOS artifacts with a stated return value. The clause 'Does not install' actively distinguishes it from the install_app sibling, so an agent can route without opening 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?

'Does not install' is an explicit boundary that implies the follow-up step (install_app) rather than this tool, and the required-parameter callout tells the agent what it must supply. It stops short of naming alternatives or stating prerequisites such as an available toolchain or whether a device/emulator is needed.

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