Skip to main content
Glama
Sign In
Xcode MCP Server

Xcode MCP Server

by r-huijts
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

generate_icon_set

Generate complete app icon sets for iOS, macOS, or watchOS from a single source image. Provide the image path and output location to create AppIcon.appiconset.

Instructions

Generate an app icon set from a source image

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": {
      "sourceImage": "<sourceImage>",
      "outputPath": "<outputPath>"
    },
    "name": "generate_icon_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoTarget platform (default: ios)
outputPathYesPath where to create the AppIcon.appiconset directory
sourceImageYesPath to the source image (should be at least 1024x1024)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/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, but it only states the action. It does not disclose side effects (e.g., creating directories, writing files), overwrite behavior, or any failure conditions. This is a significant transparency gap for a generative 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?

The description is a single, front-loaded sentence that conveys the core purpose without wasted words. It is appropriately concise for a simple tool.

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

Completeness3/5

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

The description plus schema explains the inputs but not the full scope of what 'generate an icon set' entails, such as the output structure or requirements for the source image. No output schema exists, but the tool's simplicity and strong schema descriptions keep it from being completely inadequate.

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 coverage is 100%, so all parameters are described in the input schema. The description adds no additional parameter context, but given the high schema coverage, the baseline 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's function with a specific verb ('Generate') and resource ('app icon set'), and the source input ('from a source image'). It distinguishes itself from siblings like compile_asset_catalog by focusing on generating icon sets rather than compiling them.

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?

The description implies when to use it (when you need an app icon set from an image) but provides no explicit context, prerequisites, or alternatives. There is no mention of when not to use it or comparisons to other tools.

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