Skip to main content
Glama

BCD — Bridge Control Delegate

by com.snack-wrap.bcd
OverviewDiscussionsAdmin

ios_build

Build a scheme of an Xcode project on this Mac (for the iOS Simulator unless destination says otherwise) to check that it compiles. Runs as a background job and returns its jobId; poll ios_build_status with it. Nothing is uploaded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemeYes
teamIdNoApple Developer team ID for signing, when the project has none (DEVELOPMENT_TEAM)
projectYes.xcodeproj or .xcworkspace path from ios_projects
deviceIdNoComputer name or id from list_devices. Optional with one computer online or a default set.
buildNumberNoSets CURRENT_PROJECT_VERSION
destinationNoxcodebuild -destination; default generic/platform=iOS Simulator
configurationNo
workSessionIdNoWork session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / action
      Removed value: -{
-  "enum": [
-    "build",
-    "test",
-    "archive",
-    "testflight"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / buildNumber / description
      Previous value: -"Sets CURRENT_PROJECT_VERSION; testflight defaults to a UTC timestamp so every upload is new"New value: +"Sets CURRENT_PROJECT_VERSION"
    • changedInput schema / properties / destination / description
      Previous value: -"xcodebuild -destination; tests default to the newest available iPhone simulator"New value: +"xcodebuild -destination; default generic/platform=iOS Simulator"
    • removedInput schema / properties / issuerId
      Removed value: -{
-  "description": "App Store Connect issuer ID; remembered on this Mac after the first upload",
-  "type": "string"
-}
    • removedInput schema / properties / keyId
      Removed value: -{
-  "description": "App Store Connect API key ID; the key file stays in ~/.appstoreconnect/private_keys. With it, archive and testflight let Xcode update signing profiles",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "action",
-  "project",
-  "scheme"
-]New value: +[
+  "project",
+  "scheme"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / workSessionId
      Added value: +{
+  "description": "Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.",
+  "format": "uuid",
+  "type": "string"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations mark it non-read-only, closed-world, and non-destructive, and the description adds genuinely useful behavior beyond those: it runs as a background job, returns a jobId, must be polled via ios_build_status, and uploads nothing. It could say more about failure output or build artifacts, but the async contract is well disclosed.

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?

Three tight sentences, front-loaded with the core action, then the async lifecycle, then the safety note. No padding or restatement of the name.

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 supplies the return contract (jobId) and the follow-up tool, which is the key missing piece. It is complete for invocation, though it leaves configuration/scheme semantics to 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 75% and the schema already documents project, deviceId, teamId, destination, buildNumber, and workSessionId. The description's "for the iOS Simulator unless destination says otherwise" largely restates the destination default already in the schema, so it adds little beyond the baseline.

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 scheme of an Xcode project") plus the goal (check that it compiles) and the environment (this Mac, iOS Simulator by default). An agent can distinguish it from ios_test, ios_archive, and ios_build_status 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?

Gives clear context: use it to verify compilation, and it routes the agent to ios_build_status for polling the background job. It does not explicitly contrast with alternatives like ios_test or ios_archive, so the when-not is left implicit.

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

All BCD — Bridge Control Delegate toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources