Skip to main content
Glama
Sign In
Xcode MCP Server

Xcode MCP Server

by r-huijts
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

copy_file

Copies files or directories to specified destinations, supporting recursive directory copies and relative or absolute paths.

Instructions

Copies a file or directory to a new location within allowed directories.

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": {
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "copy_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesSource path. Can be absolute, relative to active directory, or use ~ for home directory.
recursiveNoIf true, copy directories recursively
destinationYesDestination path. Can be absolute, relative to active directory, or use ~ for home directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention overwrite behavior, recursive requirements for directories, handling of existing destinations, or any side effects. The only extra info is the 'allowed directories' constraint, but it is vague.

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, concise sentence that front-loads the core purpose. It is appropriately sized, with no wasted words.

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 the lack of annotations and output schema, the description is insufficiently complete. It fails to explain key behaviors such as recursive copying requirements for directories, overwrite semantics, or how allowed directories are enforced. This is a mutation tool that requires more detail.

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 well-documented in the schema. The description does not add additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 copies a file or directory to a new location, with a specific verb and resource. It distinguishes from move_file by indicating a copy operation, and the 'within allowed directories' constraint adds useful scope.

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 like move_file, nor any preconditions or exclusions. It merely states what it does, leaving the agent to infer usage context.

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