Skip to main content
Glama
drewster99

xcode-mcp-server (drewster99)

by drewster99

get_build_results

Read-onlyIdempotent

Aggregate all build errors and warnings from Xcode builds since the last clean, ensuring you see complete results even after incremental builds.

Instructions

Get aggregated build errors and warnings from all builds since the last clean operation.

This tool addresses the issue where incremental builds only show warnings for recompiled files. It parses the build log manifest (LogStoreManifest.plist) and aggregates warnings from all builds since the last clean, excluding warnings from files that were subsequently recompiled.

Strategy:

  1. Locate the project's DerivedData/Logs/Build directory

  2. Parse LogStoreManifest.plist to find all builds since last clean

  3. For each build, parse the .xcactivitylog file to extract:

    • Warnings and errors with file/line/column/message

    • List of files compiled in that build

  4. Aggregate warnings, keeping only the most recent warning for each file

  5. If a file was recompiled in a later build, use warnings from that later build

This ensures you see all current warnings even after incremental builds.

Args: project_path: Path to an Xcode project or workspace directory max_warnings: Maximum number of warnings to show in response (default 50)

Returns: JSON string with format: { "derived_data_path": "/path/to/DerivedData/...", "summary": { "total_builds": N, "builds_since_clean": M, "builds_analyzed": K, "clean_info": "...", "total_warnings": X, "warnings_by_type": {"warnings": W, "errors": E}, "unique_files_with_warnings": F, "files_recompiled_multiple_times": R }, "aggregated_warnings": [ { "file": "/path/to/File.swift", "line": 123, "column": 45, "message": "...", "type": "warning" } ], "files_with_multiple_builds": [ { "file": "/path/to/File.swift", "builds": 3, "warnings_excluded": 2 } ], "builds_analyzed": [ { "uuid": "...", "title": "Build FunVoice", "time": 782185536.0, "warnings_found": 4, "files_compiled": 26 } ] }

Note: Only the first max_warnings warnings are included in aggregated_warnings.
The summary counts reflect the total before limiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYes
max_warningsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds detailed behavioral context: algorithm to parse logs, aggregate warnings, exclude recompiled files, and notes on only returning first max_warnings. No contradictions with annotations.

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?

The description is long but well-structured with sections: purpose, problem, strategy, args, returns, note. Every sentence adds value, though could be slightly more concise.

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?

Given the tool's complexity and lack of output schema in structured data, the description provides a complete picture: detailed algorithm, input parameters, and a full JSON return format example. It covers all necessary context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must compensate. It explains both parameters: project_path as path to Xcode project/workspace, and max_warnings with default and purpose. This adds full meaning beyond schema names and types.

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 clearly states it gets aggregated build errors and warnings from all builds since the last clean. It distinguishes itself from siblings like get_build_errors by explaining the specific problem of incremental builds only showing recompiled file warnings.

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 provides context on when to use the tool (to see all current warnings after incremental builds) but does not explicitly exclude alternatives or compare with siblings like get_build_errors. It implicitly guides usage through the problem statement.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/drewster99/xcode-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server