sl-test
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_projsC | Scans a directory (defaults to workspace root) to find Xcode project (.xcodeproj) and workspace (.xcworkspace) files. |
| list_schems_wsB | Lists available schemes in the workspace. IMPORTANT: Requires workspacePath. Example: list_schems_ws({ workspacePath: '/path/to/MyProject.xcworkspace' }) |
| list_schems_projB | Lists available schemes in the project file. IMPORTANT: Requires projectPath. Example: list_schems_proj({ projectPath: '/path/to/MyProject.xcodeproj' }) |
| list_simsB | Lists available iOS simulators with their UUIDs. |
| show_build_set_wsA | Shows build settings from a workspace using xcodebuild. IMPORTANT: Requires workspacePath and scheme. Example: show_build_set_ws({ workspacePath: '/path/to/MyProject.xcworkspace', scheme: 'MyScheme' }) |
| show_build_set_projB | Shows build settings from a project file using xcodebuild. IMPORTANT: Requires projectPath and scheme. Example: show_build_set_proj({ projectPath: '/path/to/MyProject.xcodeproj', scheme: 'MyScheme' }) |
| clean_wsA | Cleans build products for a specific workspace using xcodebuild. IMPORTANT: Requires workspacePath. Scheme/Configuration are optional. Example: clean_ws({ workspacePath: '/path/to/MyProject.xcworkspace', scheme: 'MyScheme' }) |
| clean_projB | Cleans build products for a specific project file using xcodebuild. IMPORTANT: Requires projectPath. Scheme/Configuration are optional. Example: clean_proj({ projectPath: '/path/to/MyProject.xcodeproj', scheme: 'MyScheme' }) |
| swift_package_buildC | Builds a Swift Package with swift build |
| swift_package_testC | Runs tests for a Swift Package with swift test |
| swift_package_runB | Runs an executable target from a Swift Package with swift run |
| swift_package_stopA | Stops a running Swift Package executable started with swift_package_run |
| swift_package_listB | Lists currently running Swift Package processes |
| swift_package_cleanC | Cleans Swift Package build artifacts and derived data |
| build_mac_wsC | Builds a macOS app using xcodebuild from a workspace. |
| build_mac_projC | Builds a macOS app using xcodebuild from a project file. |
| build_run_mac_wsC | Builds and runs a macOS app from a workspace in one step. |
| build_run_mac_projB | Builds and runs a macOS app from a project file in one step. |
| build_ios_sim_name_wsB | Builds an iOS app from a workspace for a specific simulator by name. IMPORTANT: Requires workspacePath, scheme, and simulatorName. Example: build_ios_sim_name_ws({ workspacePath: '/path/to/MyProject.xcworkspace', scheme: 'MyScheme', simulatorName: 'iPhone 16' }) |
| build_ios_sim_name_projB | Builds an iOS app from a project file for a specific simulator by name. IMPORTANT: Requires projectPath, scheme, and simulatorName. Example: build_ios_sim_name_proj({ projectPath: '/path/to/MyProject.xcodeproj', scheme: 'MyScheme', simulatorName: 'iPhone 16' }) |
| build_ios_sim_id_wsB | Builds an iOS app from a workspace for a specific simulator by UUID. IMPORTANT: Requires workspacePath, scheme, and simulatorId. Example: build_ios_sim_id_ws({ workspacePath: '/path/to/MyProject.xcworkspace', scheme: 'MyScheme', simulatorId: 'SIMULATOR_UUID' }) |
| build_ios_sim_id_projB | Builds an iOS app from a project file for a specific simulator by UUID. IMPORTANT: Requires projectPath, scheme, and simulatorId. Example: build_ios_sim_id_proj({ projectPath: '/path/to/MyProject.xcodeproj', scheme: 'MyScheme', simulatorId: 'SIMULATOR_UUID' }) |
| build_run_ios_sim_name_wsB | Builds and runs an iOS app from a workspace on a simulator specified by name. IMPORTANT: Requires workspacePath, scheme, and simulatorName. Example: build_run_ios_sim_name_ws({ workspacePath: '/path/to/workspace', scheme: 'MyScheme', simulatorName: 'iPhone 16' }) |
| build_run_ios_sim_name_projB | Builds and runs an iOS app from a project file on a simulator specified by name. IMPORTANT: Requires projectPath, scheme, and simulatorName. Example: build_run_ios_sim_name_proj({ projectPath: '/path/to/project.xcodeproj', scheme: 'MyScheme', simulatorName: 'iPhone 16' }) |
| build_run_ios_sim_id_wsA | Builds and runs an iOS app from a workspace on a simulator specified by UUID. IMPORTANT: Requires workspacePath, scheme, and simulatorId. Example: build_run_ios_sim_id_ws({ workspacePath: '/path/to/workspace', scheme: 'MyScheme', simulatorId: 'SIMULATOR_UUID' }) |
| build_run_ios_sim_id_projA | Builds and runs an iOS app from a project file on a simulator specified by UUID. IMPORTANT: Requires projectPath, scheme, and simulatorId. Example: build_run_ios_sim_id_proj({ projectPath: '/path/to/project.xcodeproj', scheme: 'MyScheme', simulatorId: 'SIMULATOR_UUID' }) |
| build_ios_dev_wsA | Builds an iOS app from a workspace for a physical device. IMPORTANT: Requires workspacePath and scheme. Example: build_ios_dev_ws({ workspacePath: '/path/to/MyProject.xcworkspace', scheme: 'MyScheme' }) |
| build_ios_dev_projB | Builds an iOS app from a project file for a physical device. IMPORTANT: Requires projectPath and scheme. Example: build_ios_dev_proj({ projectPath: '/path/to/MyProject.xcodeproj', scheme: 'MyScheme' }) |
| get_mac_app_path_wsB | Gets the app bundle path for a macOS application using a workspace. IMPORTANT: Requires workspacePath and scheme. Example: get_mac_app_path_ws({ workspacePath: '/path/to/workspace', scheme: 'MyScheme' }) |
| get_mac_app_path_projA | Gets the app bundle path for a macOS application using a project file. IMPORTANT: Requires projectPath and scheme. Example: get_mac_app_path_proj({ projectPath: '/path/to/project.xcodeproj', scheme: 'MyScheme' }) |
| get_ios_dev_app_path_wsA | Gets the app bundle path for an iOS physical device application using a workspace. IMPORTANT: Requires workspacePath and scheme. Example: get_ios_dev_app_path_ws({ workspacePath: '/path/to/workspace', scheme: 'MyScheme' }) |
| get_ios_dev_app_path_projA | Gets the app bundle path for an iOS physical device application using a project file. IMPORTANT: Requires projectPath and scheme. Example: get_ios_dev_app_path_proj({ projectPath: '/path/to/project.xcodeproj', scheme: 'MyScheme' }) |
| get_sim_app_path_name_wsB | Gets the app bundle path for a simulator by name using a workspace. IMPORTANT: Requires workspacePath, scheme, platform, and simulatorName. Example: get_sim_app_path_name_ws({ workspacePath: '/path/to/workspace', scheme: 'MyScheme', platform: 'iOS Simulator', simulatorName: 'iPhone 16' }) |
| get_sim_app_path_name_projB | Gets the app bundle path for a simulator by name using a project file. IMPORTANT: Requires projectPath, scheme, platform, and simulatorName. Example: get_sim_app_path_name_proj({ projectPath: '/path/to/project.xcodeproj', scheme: 'MyScheme', platform: 'iOS Simulator', simulatorName: 'iPhone 16' }) |
| get_sim_app_path_id_wsA | Gets the app bundle path for a simulator by UUID using a workspace. IMPORTANT: Requires workspacePath, scheme, platform, and simulatorId. Example: get_sim_app_path_id_ws({ workspacePath: '/path/to/workspace', scheme: 'MyScheme', platform: 'iOS Simulator', simulatorId: 'SIMULATOR_UUID' }) |
| get_sim_app_path_id_projA | Gets the app bundle path for a simulator by UUID using a project file. IMPORTANT: Requires projectPath, scheme, platform, and simulatorId. Example: get_sim_app_path_id_proj({ projectPath: '/path/to/project.xcodeproj', scheme: 'MyScheme', platform: 'iOS Simulator', simulatorId: 'SIMULATOR_UUID' }) |
| boot_simB | Boots an iOS simulator. IMPORTANT: You MUST provide the simulatorUuid parameter. Example: boot_sim({ simulatorUuid: 'YOUR_UUID_HERE' }) |
| open_simC | Opens the iOS Simulator app. |
| set_sim_appearanceB | Sets the appearance mode (dark/light) of an iOS simulator. |
| set_simulator_locationC | Sets a custom GPS location for the simulator. |
| reset_simulator_locationC | Resets the simulator's location to default. |
| set_network_conditionC | Simulates different network conditions (e.g., wifi, 3g, edge, high-latency, dsl, 100%loss, 3g-lossy, very-lossy) in the simulator. |
| reset_network_conditionC | Resets network conditions to default in the simulator. |
| install_app_simA | Installs an app in an iOS simulator. IMPORTANT: You MUST provide both the simulatorUuid and appPath parameters. Example: install_app_sim({ simulatorUuid: 'YOUR_UUID_HERE', appPath: '/path/to/your/app.app' }) |
| launch_app_simA | Launches an app in an iOS simulator. IMPORTANT: You MUST provide both the simulatorUuid and bundleId parameters. Note: You must install the app in the simulator before launching. The typical workflow is: build → install → launch. Example: launch_app_sim({ simulatorUuid: 'YOUR_UUID_HERE', bundleId: 'com.example.MyApp' }) |
| launch_app_logs_simC | Launches an app in an iOS simulator and captures its logs. |
| get_mac_bundle_idA | Extracts the bundle identifier from a macOS app bundle (.app). IMPORTANT: You MUST provide the appPath parameter. Example: get_mac_bundle_id({ appPath: '/path/to/your/app.app' }) Note: In some environments, this tool may be prefixed as mcp0_get_macos_bundle_id. |
| get_ios_bundle_idA | Extracts the bundle identifier from an iOS app bundle (.app). IMPORTANT: You MUST provide the appPath parameter. Example: get_ios_bundle_id({ appPath: '/path/to/your/app.app' }) Note: In some environments, this tool may be prefixed as mcp0_get_ios_bundle_id. |
| launch_mac_appB | Launches a macOS application. IMPORTANT: You MUST provide the appPath parameter. Example: launch_mac_app({ appPath: '/path/to/your/app.app' }) Note: In some environments, this tool may be prefixed as mcp0_launch_macos_app. |
| start_sim_log_capA | Starts capturing logs from a specified simulator. Returns a session ID. By default, captures only structured logs. |
| stop_sim_log_capA | Stops an active simulator log capture session and returns the captured logs. |
| screenshotB | Captures screenshot for visual verification. For UI coordinates, use describe_ui instead (don't determine coordinates from screenshots). |
| scaffold_ios_projectB | Scaffold a new iOS project from templates. Creates a modern Xcode project with workspace structure, SPM package for features, and proper iOS configuration. |
| scaffold_macos_projectB | Scaffold a new macOS project from templates. Creates a modern Xcode project with workspace structure, SPM package for features, and proper macOS configuration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 54 tools
The tools have overlapping purposes due to excessive specialization, such as multiple build tools for iOS simulators with minor variations (by UUID vs. name, project vs. workspace). While descriptions clarify parameters, the sheer number of similar tools creates ambiguity and increases the risk of misselection, as agents must navigate many near-identical options.
Tool names follow a consistent snake_case pattern with clear verb_noun structures, such as 'build_ios_dev_proj' or 'get_sim_app_path_id_ws'. However, minor inconsistencies exist, like 'boot_sim' using a shorter form compared to others, and some tools like 'scaffold_ios_project' deviate slightly in word order, but overall the naming is predictable and readable.
With 54 tools, the count is excessive for the domain of iOS/macOS development and testing. This bloats the tool surface, making it cumbersome for agents to navigate and increasing cognitive load. A more streamlined set with fewer, more generalized tools would be more appropriate and user-friendly.
The tool set comprehensively covers the iOS/macOS development lifecycle, including project scaffolding, building, cleaning, running, simulator management, logging, and Swift package operations. There are no obvious gaps; agents can perform end-to-end workflows from creation to testing and deployment without dead ends.