Xcode MCP Server

Overview Schema Source Related Servers Discussions Admin

xcode_test_project

Execute tests for Xcode projects by specifying the project path and test scheme to validate iOS/macOS application functionality.

Instructions

Run tests for an Xcode project

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_path": "<project_path>",
      "scheme": "<scheme>"
    },
    "name": "xcode_test_project"
  }
}

Input Schema

Name	Required	Description
`project_path`	Yes	Path to .xcodeproj file
`scheme`	Yes	Test scheme name
`destination`	No	Test destination

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Run tests' but doesn't disclose behavioral traits such as whether this requires specific Xcode setup, if it's destructive (e.g., modifies project files), execution time, error handling, or output format. This leaves significant gaps for an agent to understand the tool's behavior.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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

Completeness2/5

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

Given no annotations, no output schema, and a mutation-like action ('Run tests'), the description is incomplete. It doesn't cover behavioral aspects, return values, or error conditions, which are crucial for an agent to use this tool effectively in a development context.

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%, with clear parameter descriptions in the input schema. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or default behaviors. With high schema coverage, the baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Run tests for an Xcode project' clearly states the action (run tests) and resource (Xcode project), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'xcode_run_on_device' or 'xcode_build_project', which might also involve testing scenarios, so it misses full sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'xcode_run_on_device' or 'xcode_build_project' that could relate to testing, there's no indication of context, prerequisites, or exclusions, leaving usage ambiguous.

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