Skip to main content
Glama
Sign In
Xcode MCP Server

Xcode MCP Server

by r-huijts
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_available_destinations

Find available build destinations for your Xcode project or workspace. Optionally specify a scheme to filter the list of destinations.

Instructions

Lists available build destinations for the active Xcode project or workspace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_available_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemeNoOptional scheme to show destinations for. If not provided, uses the active scheme.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description is the sole source of behavioral information. 'Lists' clearly indicates a read-only, non-mutating operation, and the optional scheme behavior is disclosed. It does not mention error conditions or output formats, but for a simple listing operation this is not a major gap.

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?

The description is a single, focused sentence that states what the tool does and its context. Every word contributes to understanding the tool's purpose and scope, with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one optional parameter and no output schema. The description covers the core action, the scope (active project/workspace), and the optional scheme behavior, making it complete for effective selection and invocation.

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?

The schema covers the single parameter 100%, including its optional nature and default behavior ('Optional scheme to show destinations for. If not provided, uses the active scheme.'). The description does not add material meaning beyond the schema, so the baseline score of 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?

The description uses a specific verb ('Lists') and names the resource ('available build destinations') with the scope ('active Xcode project or workspace'). It clearly distinguishes from sibling tools like list_available_schemes by targeting a different resource.

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?

The description clearly identifies when to use the tool: to list build destinations for the active project or workspace. It also explains the scheme parameter's default behavior, which gives useful context, though it does not explicitly compare against alternatives or state exclusion cases.

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