Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

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
session_startA

Report whether this server adopted a simulator left by an earlier session or started clean. Use reset: true to terminate the adopted simulator and clear the stored session.

simulator_statusA

Inspect Connect IQ simulator process status, window ID, bounds, macOS Screen Recording and Accessibility permissions, TCP port 1234 status, and active device profile metadata.

launch_simulatorA

Launch the Garmin Connect IQ simulator, by default on a hidden Windows desktop where button input does not change your foreground window.

list_devicesA

List all installed Garmin device profiles in Connect IQ SDK Devices directory with display resolutions, touch support, screen shape, and available buttons.

set_active_deviceA

Set the active Garmin device ID for subsequent simulator commands, button presses, touch gestures, and screenshot cropping.

dev_loopA

Build the project, run it, capture the first stable frame and return the latest log lines in one call.

build_appC

Build a Monkey C project for a specified device using the SDK monkeyc compiler.

run_appB

Push and run a compiled Monkey C executable (.prg) on the active device in the simulator using monkeydo, and stream logs.

stop_appB

Stop the currently running Garmin Monkey C app process in the simulator.

run_unit_testsA

Run Monkey C unit tests for a compiled .prg test binary in the simulator using monkeydo -t.

press_buttonB

Press a physical bezel button on the active Garmin device (e.g. 'select', 'back', 'up', 'down', 'menu'). Supports short clicks or long-press holds, and returns the updated watch screen.

press_button_sequenceA

Execute a sequence of button presses in order with configurable delays, capturing the final watch screen.

send_keyC

Send a platform virtual key code or named key ('enter', 'esc', 'up', 'down', 'menu', 'space') to the Connect IQ simulator window.

tap_screenB

Tap the watch touchscreen at specific display coordinates (X, Y) or normalized coordinates (0.0..1.0).

swipe_screenB

Synthesize a touch drag gesture on the watch display in a cardinal direction ('up', 'down', 'left', 'right'), adhering to device gesture thresholds.

hold_screenB

Long-press at specific coordinates on the watch touchscreen (e.g. to open a watchface complication or menu).

get_screenshotB

Capture a screenshot of the Connect IQ simulator. Supports watch display crop ('screen', 1:1 pixel mapping), full window with bezel ('bezel'), or annotated debug view with button hitboxes and coordinate grid ('annotated').

get_app_logsA

Retrieve console output, System.println logs, and crash traces from the running Monkey C application and simulator. Logs are also appended to a session file, so a reconnect does not lose history.

trigger_menu_actionC

Trigger a macOS menu item in ConnectIQ.app via Accessibility (AXUIElement), such as simulation data or activity settings.

set_glance_modeB

Toggle or set the simulator Glance View mode (Settings > Glance View) for testing widget glance summaries.

inspect_uiA

Read simulator Accessibility hierarchy, including menus and native dialogs. Pass hwnd to inspect a dialog from list_windows. Paths are ephemeral: inspect before acting.

act_on_uiB

Act on a freshly inspected native simulator element. set writes AXValue; AXPress activates controls. Pass hwnd for dialogs.

snapshot_app_filesB

Back up only files matching explicit PRG basenames from simulator APPS. Does not stop the app; use an idle/stopped session.

restore_app_filesA

Restore a verified app-scoped snapshot. Requires explicit confirmation and a stopped app; never use while app/background writes are active.

terminate_simulatorB

Terminate only ConnectIQ.app and destroy its isolated desktop if one was used. Force is for an unresponsive simulator. Does not delete stored data.

recognize_image_textA

Recognize text in a saved simulator PNG using on-device OCR. Returns text and normalized bounds; confidence is available on macOS. OCR is evidence, not a replacement for storage assertions.

close_storage_editorA

Close the simulator's persistent-storage editor and verify the window is gone. Safe when already closed.

place_windowB

Move or clamp the simulator window inside the nearest monitor work area. With no coordinates it only rescues a window that is mostly off-screen.

wait_for_stableA

Wait until two consecutive simulator captures are identical, so screenshots and assertions are not taken mid-animation.

diff_screenshotA

Compare a baseline PNG with another PNG or with the current simulator screen. Returns the changed percentage and the bounding box of change.

doctorB

Check the SDK, toolchain, device profiles, developer key, simulator window, occlusion and session log before blaming an app failure on the app.

debug_statusA

Report the local debug channel endpoint, whether the app has polled it, and the last command result.

debug_pingA

Round-trip a ping through the in-app debug channel. Proves the app is running and polling without touching focus.

state_readA

Read the app's storage and property state through the in-app debug channel. Values are scalar summaries; arrays report size.

state_seedB

Write storage keys through the in-app debug channel, then optionally read them back to verify. Use null to delete a key.

state_resetB

Clear every app storage key through the in-app debug channel and optionally report the resulting state.

set_timeB

Shift the app's clock through the debug channel. Use an ISO timestamp or an offset in seconds. Only code paths using DebugClock follow the offset.

debug_commandB

Send a raw command to the in-app debug channel. Verbs: ping, state, seed, premium, deck_list, list, map, time, phone, reset; arguments are semicolon-free strings.

phone_messageA

Deliver a phone-app message to the running app through the debug channel and let the app handler store it. Use state_read to verify last_phone_message.

list_windowsA

List top-level simulator windows, including storage, login, time and phone-message dialogs. IME and hidden wx windows are filtered unless include_hidden is true.

capture_windowA

Capture a simulator-owned dialog or window by hwnd. Returns the PNG image and optional saved path.

close_windowA

Close a simulator-owned dialog by hwnd. Refuses to close the main simulator window.

reset_stateA

Reset persisted app data through the simulator menu, with a screenshot and optional APPS snapshot first. Requires confirm: true. Restart the app afterwards to observe a clean launch.

matrix_runB

Build, run and capture one screen per device, optionally run a button/touch scenario, and compare each step against .ciq/baselines. Creates baselines when missing or when update_baselines is true.

matrix_diffC

Compare every baseline PNG in a directory with the matching current PNG and report changed percentage and bounds.

calibrateB

Report window, bezel and display geometry plus every button centre mapped to screen coordinates, and check each point is inside the window. Optionally save a raw screenshot.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 46 tools

Disambiguation3/5

The broad domains are distinct (lifecycle, input, capture, debug, files), but several boundaries blur: debug_command overlaps state_read/state_seed/state_reset/set_time/phone_message, and reset_state/state_reset/debug_command reset all touch reset behavior. matrix_run vs. build+run vs. dev_loop, and capture_window/get_screenshot/diff_screenshot also require careful reading to choose correctly.

Naming Consistency4/5

Names are consistently snake_case and mostly action-oriented, which makes the set readable. The pattern varies between verb_noun (get_screenshot, list_devices), noun_verb (session_start, state_read, simulator_status), and bare utility names (doctor, calibrate), but this is a minor deviation rather than a different convention.

Tool Count2/5

At 46 tools, the surface is heavy for a simulator-control server, with many one-off diagnostic, matrix, window, and debug helpers. While the domain is genuinely broad, the count exceeds a well-scoped set and invites tool-selection overhead.

Completeness4/5

Coverage is strong across lifecycle, build/run, input simulation, screenshots/diffs, debug-channel state, file snapshots, windows, and diagnostics. Minor gaps remain around explicit baseline management (listing/deleting baselines) and app install/uninstall-style operations, but core workflows are well supported.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues