Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

xcodebuild-get-details

Retrieve on-demand full build or test logs from cached results. Filter to errors, warnings, summary, command, or metadata for fast debugging without overwhelming initial responses.

Instructions

xcodebuild-get-details

🔍 Retrieve detailed build or test output from cached results - Progressive disclosure for logs.

Provides on-demand access to full build and test logs that were cached during xcodebuild-build or xcodebuild-test execution. Implements progressive disclosure pattern: initial build/test responses return concise summaries to prevent token overflow, while this tool allows drilling down into full logs, filtered errors, warnings, or metadata when needed for debugging.

Advantages

• Access full build logs without cluttering initial responses • Filter to just errors or warnings for faster debugging • Retrieve exact command executed and exit code • Inspect build metadata and cache information

Parameters

Required

  • buildId (string): Cache ID from xcodebuild-build or xcodebuild-test response

  • detailType (string): Type of details to retrieve

    • "full-log": Complete stdout and stderr output

    • "errors-only": Lines containing errors or build failures

    • "warnings-only": Lines containing warnings

    • "summary": Build metadata and configuration used

    • "command": Exact xcodebuild command executed

    • "metadata": Cache info and output sizes

Optional

  • maxLines (number): Maximum lines to return (default: 100)

Returns

  • Tool execution results with requested build or test details

  • Full logs or filtered errors/warnings with line counts

  • Build metadata and execution information

Related Tools

  • xcodebuild-build: Build iOS projects (returns buildId)

  • xcodebuild-test: Run tests (returns testId)

  • simctl-get-details: Get simulator list details

Notes

  • Tool is auto-registered with MCP server

  • Requires valid cache ID from recent build/test

  • Cache IDs expire after 30 minutes

  • Use for debugging build failures and test issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buildIdYes
detailTypeYes
maxLinesNo

Tool Definition Quality

A5/5.0
Behavior5/5

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

No annotations provided, but the description thoroughly discloses behavioral traits: it retrieves cached results, uses progressive disclosure to avoid token overflow, and notes cache ID expiration. It also mentions auto-registration with MCP server.

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 well-structured with headings, bullet points, and emojis. Every section adds necessary value without redundancy. It is appropriately sized for the tool's complexity.

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?

Despite no output schema, the description covers return values (tool execution results, filtered logs, metadata). It also includes notes on cache ID expiration and usage, making it complete for a tool with moderate complexity.

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?

The input schema provides minimal descriptions, but the description compensates with detailed explanations of each parameter, including the enum values for detailType and default value for maxLines. Schema description coverage is 0%, but the description adds full meaning.

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 the tool retrieves detailed build/test output from cached results, implementing a progressive disclosure pattern for logs. It is distinct from sibling tools like xcodebuild-build and xcodebuild-test, which produce the initial summaries.

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?

The description explains when to use this tool (for debugging build failures/test issues) and mentions related tools and requirements (valid cache ID, 30-minute expiration). It also lists alternative tools in the 'Related Tools' section.

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/conorluddy/xc-mcp'

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