BCD — Bridge Control Delegate

ios_projects

Read-only

Find the Xcode projects and workspaces on this Mac and, for one of them, list its schemes and build configurations. Start here before ios_build, ios_test, ios_archive or ios_testflight.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`project`	No	An .xcodeproj or .xcworkspace path to list schemes for
`deviceId`	No	Computer name or id from list_devices. Optional with one computer online or a default set.
`directory`	No	Folder to search, e.g. ~/Projects	~
`workSessionId`	No	Work 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.

Changed1 schema field changedSep 30, 2026

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"
+}

First observedSep 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: the tool has two modes (enumerate all projects vs. list schemes for one) and is a read-only discovery entry point. It doesn't mention rate limits or output shape, but against existing annotations this is above baseline.

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 sentences, zero filler, and the primary discovery behavior is front-loaded ahead of the workflow-ordering cue. Every clause earns 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?

For a 0-required-parameter, read-only discovery tool with full schema coverage and no output schema, the description covers purpose, two operation modes, and sequencing. It could say more about what a no-argument call returns, but nothing essential to correct invocation is missing.

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 the schema already documents all four parameters in detail (project path, deviceId source, directory, workSessionId). The description mentions the 'one of them' listing behavior that corresponds to the project param but adds no syntax or format detail beyond the schema. 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 ('Find the Xcode projects and workspaces on this Mac') and clarifies the second mode of operation ('for one of them, list its schemes and build configurations'). It explicitly names the sibling tools it precedes, so an agent can distinguish it from ios_build/ios_test 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 Guidelines5/5

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

'Start here before ios_build, ios_test, ios_archive or ios_testflight' gives explicit ordering guidance and names all four alternative tools. The agent knows exactly when to reach for this tool rather than a downstream build/test tool.

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 tools Inspect

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

Need Help?