Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_simsA

List available simulator devices (udid, name, state, runtime).

boot_simB

Boot a simulator. Defaults to the already-booted sim, else the first available iPhone.

install_appB

Install a built .app bundle onto the simulator.

launchA

Launch an installed app by bundle id. Returns the launch output (pid).

terminateC

Terminate a running app by bundle id.

reset_appC

Uninstall then reinstall an app for a clean state.

deeplinkB

Open a URL / universal link in the simulator (jump straight to a screen).

set_permissionB

Grant/revoke/reset a privacy permission for an app (e.g. photos, camera, location, notifications).

describe_uiA

PRIMARY PERCEPTION. Return the accessibility tree of the current screen as a list of elements (label, type, value, enabled, frame). Reason over this and tap by label.

screenshotA

Capture a PNG screenshot of the current screen. Use as the vision fallback when an element is not exposed in the accessibility tree, or to verify state.

tapA

Tap an element by accessibility label (preferred) or by raw x,y coordinate (fallback). Provide either label or both x and y.

type_textB

Type text into the currently focused field. Tap the field first to focus it.

swipeA

Swipe/scroll from one point to another. Either give a direction (auto-computed from screen center) or explicit from/to coordinates.

press_buttonC

Press a hardware button (HOME backgrounds the app; LOCK locks the screen).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 14 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: simulator management (boot_sim, list_sims), app lifecycle (install_app, launch, terminate, reset_app), interaction (tap, swipe, type_text, press_button), perception (describe_ui, screenshot), and configuration (set_permission, deeplink). No two tools overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent lowercase underscore convention (snake_case) with imperative verbs (e.g., boot_sim, install_app, describe_ui). The pattern is uniform across all 14 tools, enhancing predictability.

Tool Count5/5

14 tools is well-scoped for an iOS simulator driver, covering essential operations: setup, app management, interaction, perception, and configuration. The count is neither excessive nor insufficient for the domain.

Completeness4/5

The toolset covers core simulator workflows: app install/launch/terminate/reset, UI interaction (tap, swipe, type), perception (accessibility tree, screenshot), and permissions. Minor gaps exist (e.g., no dedicated uninstall or app state query), but agents can work around them.

Maintenance

ActivityStale
ResponsivenessNo issues