Skip to main content
Glama
Sign In
Xcode MCP Server

Xcode MCP Server

by r-huijts
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

clean_swift_package

Remove Swift Package build artifacts to resolve build issues and free disk space, with options to reset the build directory or purge the global cache.

Instructions

Cleans the build artifacts of a Swift Package.

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": "clean_swift_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
resetNoReset the complete build directory
purgeCacheNoAlso purge the global cache

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action without mentioning that cleaning is destructive, removes derived data, or affects global cache. This is a significant gap for a mutation tool.

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?

A single concise sentence that is front-loaded and contains no filler. Every word adds value.

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

Completeness4/5

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

The tool is simple with two optional boolean parameters fully described in the schema. The description states the purpose adequately for selection and invocation. No output schema is needed. Minor lack is not mentioning side effects, but that is covered under behavioral transparency.

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%, so the parameters are already well-documented (e.g., 'Reset the complete build directory', 'Also purge the global cache'). The description adds no additional parameter meaning, but the baseline 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 ('Cleans') and resource ('build artifacts of a Swift Package'), clearly distinguishing it from sibling tool 'clean_project' which targets Xcode projects.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. The description implies usage for Swift Package build artifacts but does not mention exclusions or compare with sibling tools like 'clean_project'.

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