Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

cache

Retrieve metrics, inspect and adjust age limits, and purge data for simulators, projects, or responses to optimize Xcode tool performance and handle large outputs.

Instructions

cache

Unified cache management - get statistics, get configuration, set configuration, clear cache.

Overview

Single tool for cache management. Routes to specialized handlers while maintaining clean operation semantics.

Operations

get-stats

Get cache statistics and metrics.

Example:

await cacheTool({ operation: 'get-stats' })

Returns: Cache statistics including size, hit rates, and usage metrics.

get-config

Get cache configuration for specific cache type.

Parameters:

  • cacheType (string, optional): Cache type - 'simulator', 'project', 'response', or 'all'

Example:

await cacheTool({
  operation: 'get-config',
  cacheType: 'simulator'
})

Returns: Current configuration including max age settings.

set-config

Set cache configuration.

Parameters:

  • cacheType (string): Cache type - 'simulator', 'project', 'response', or 'all'

  • maxAgeMs (number, optional): Maximum age in milliseconds

  • maxAgeMinutes (number, optional): Maximum age in minutes

  • maxAgeHours (number, optional): Maximum age in hours

Example:

await cacheTool({
  operation: 'set-config',
  cacheType: 'simulator',
  maxAgeHours: 2
})

clear

Clear cache for specific type.

Parameters:

  • cacheType (string, optional): Cache type - 'simulator', 'project', 'response', or 'all'

Example:

await cacheTool({
  operation: 'clear',
  cacheType: 'simulator'
})

Cache Types

  • simulator: Simulator list and state cache

  • project: Project configuration and build settings cache

  • response: Large response output cache for progressive disclosure

  • all: All caches (default when not specified)

Related Tools

  • list-cached-responses: View cached response IDs

  • xcodebuild-get-details: Retrieve cached build output

  • simctl-get-details: Retrieve cached simulator details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
cacheTypeNo
maxAgeMsNo
maxAgeMinutesNo
maxAgeHoursNo

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Despite no annotations, the description thoroughly explains each operation's behavior, input/output, and cache types. It includes examples and return descriptions, though it lacks details on side effects (e.g., clearing cache) or error conditions.

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 well-organized with headings, sections, and examples. It is detailed but not overly verbose; however, some redundancy exists (e.g., cache types listed in two places).

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?

All four operations are fully documented with parameters, examples, and return descriptions. Related tools are mentioned for context. Despite the absence of output schema, the description adequately covers what to expect.

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?

With 0% schema description coverage, the description adds significant value by explaining each parameter, including the enum options for operation and cacheType, and the meaning of maxAgeMs/Minutes/Hours. Examples further clarify usage.

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 'Unified cache management' and enumerates all operations (get-stats, get-config, set-config, clear). It distinguishes from sibling tools like list-cached-responses by mentioning them as related tools, showing differentiation.

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?

Each operation is explained with examples and parameter details, providing clear context for when to use each. The 'Related Tools' section offers guidance on alternatives, though it could be more explicit about when not to use this tool.

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