Skip to main content
Glama
ebowwa

Xcode MCP Server

by ebowwa

xcode_show_sdk_info

Display available Xcode SDKs and their file paths to help developers identify and access development platforms for iOS and macOS projects.

Instructions

Show available SDKs and their paths

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the tool logic for xcode_show_sdk_info by stripping the 'xcode_' prefix to get 'show_sdk_info', calling CommandExecutor.executeCommand, and formatting the output response.
    // Handle Xcode commands
    // Remove 'xcode_' prefix if present
    const commandName = name.startsWith('xcode_') ? name.slice(6) : name;
    const result = await this.commandExecutor.executeCommand(commandName, args);
    
    let responseText = result.output;
    if (result.error) {
      responseText += `\n\nWarnings/Errors:\n${result.error}`;
    }
    if (!result.success) {
      responseText = `Command failed: ${result.error}\n\nCommand executed: ${result.command}`;
    }
    
    return {
      content: [
        {
          type: 'text',
          text: responseText,
        },
      ],
    };
  • Dynamically generates the tool name 'xcode_show_sdk_info' (from command 'show_sdk_info') and its inputSchema based on the command parameters definition.
    generateMCPToolDefinitions(): Array<{
      name: string;
      description: string;
      inputSchema: any;
    }> {
      return Object.entries(this.commands).map(([name, command]) => ({
        name: `xcode_${name}`,
        description: command.description,
        inputSchema: {
          type: 'object',
          properties: command.parameters ? Object.fromEntries(
            Object.entries(command.parameters).map(([paramName, paramDef]) => [
              paramName,
              {
                type: paramDef.type,
                description: paramDef.description,
                ...(paramDef.default !== undefined && { default: paramDef.default })
              }
            ])
          ) : {},
          required: command.parameters ? Object.entries(command.parameters)
            .filter(([_, paramDef]) => paramDef.required)
            .map(([paramName]) => paramName) : []
        }
      }));
    }
  • src/index.ts:87-89 (registration)
    Registers the ListToolsRequestSchema handler which returns the list of available tools including 'xcode_show_sdk_info'.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [...tools, ...webMonitorTools],
    }));
  • Core execution logic for the 'show_sdk_info' command: validates params, builds shell command by templating, executes via child_process.exec, returns stdout/stderr.
    async executeCommand(name: string, args: Record<string, any> = {}): Promise<{
      success: boolean;
      output: string;
      error?: string;
      command: string;
    }> {
      const command = this.getCommand(name);
      if (!command) {
        throw new Error(`Command '${name}' not found`);
      }
    
      this.validateParameters(command, args);
    
      // Handle internal commands
      if (command.command.startsWith('internal:')) {
        return await this.executeInternalCommand(command, args);
      }
    
      // Handle external commands
      const builtCommand = this.buildCommand(command, args);
    
      try {
        const { stdout, stderr } = await execAsync(builtCommand);
        
        return {
          success: true,
          output: stdout,
          error: stderr || undefined,
          command: builtCommand
        };
      } catch (error) {
        return {
          success: false,
          output: '',
          error: error instanceof Error ? error.message : String(error),
          command: builtCommand
        };
      }
    }
  • Builds the actual shell command string for execution by replacing placeholders {param} in the command template from commands.json with provided arguments.
    buildCommand(command: XcodeCommand, args: Record<string, any>): string {
      let builtCommand = command.command;
    
      // Replace required parameters
      if (command.parameters) {
        for (const [paramName, paramDef] of Object.entries(command.parameters)) {
          const value = args[paramName] !== undefined ? args[paramName] : paramDef.default;
          
          if (paramDef.type === 'boolean') {
            // Handle boolean parameters
            if (value === true) {
              // Replace placeholder with the template if true
              builtCommand = builtCommand.replace(`{${paramName}}`, paramDef.template || '');
            } else {
              // Remove placeholder if false
              builtCommand = builtCommand.replace(`{${paramName}}`, '');
            }
          } else if (value !== undefined && value !== null && value !== '') {
            if (paramDef.template) {
              // Use custom template for parameter
              const paramValue = paramDef.template.replace(`{${paramName}}`, value);
              builtCommand = builtCommand.replace(`{${paramName}}`, paramValue);
            } else {
              // Direct replacement
              builtCommand = builtCommand.replace(`{${paramName}}`, value);
            }
          } else {
            // Remove optional parameter placeholders
            builtCommand = builtCommand.replace(new RegExp(`\\s*\\{${paramName}\\}`, 'g'), '');
          }
        }
      }
    
      // Clean up any remaining placeholder patterns
      builtCommand = builtCommand.replace(/\s+/g, ' ').trim();
      
      return builtCommand;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but doesn't describe what 'Show' entails (e.g., output format, whether it's read-only, potential errors, or side effects). For a tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the tool has no parameters, no annotations, and no output schema, the description is minimal but covers the basic action. However, it lacks details on behavior, output, or usage context, which are needed for a complete understanding, especially without structured data to compensate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it meets the baseline expectation for a parameterless tool, but doesn't exceed it with extra context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Show' and the resource 'available SDKs and their paths', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'xcode_show_build_settings' or 'xcode_show_destinations', which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, typical scenarios, or exclusions, leaving the agent to infer usage from the tool name alone.

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/ebowwa/xcode-mcp'

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