Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LAGSMITH_APPNoPath to your copy of Lagsmith. Set this if Lagsmith isn't in /Applications or ~/Applications.
LAGSMITH_PORTNoPort of Lagsmith's automation server on 127.0.0.1 (default 47300). Set LAGSMITH_PORT to change the port.47300

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Lagsmith runs on macOS only (macOS 13 Ventura or later). See https://lagsmith.com/download.

Lagsmith slows down and breaks the network of individual apps on this Mac: iOS Simulator apps and Mac apps. Only the apps you target are affected, so your own connection, the terminal and test runners stay at full speed. Use it to test how an app copes with a slow or failing network, for example before or during end-to-end and UI tests.

Typical flow: list_targets to find the app's bundle ID and simulator; set_network with a preset like 3G or a failure like airplane; relaunch_app so every connection the app makes goes through the new conditions (needed the first time, and gives request monitoring); run the tests or use the app; get_requests to see what the app actually sent and got back; reset_network when done. fail_endpoint and mock_endpoint break or fake one endpoint while the rest works.

For simulator apps pass simulator: "booted" (the running simulator), a device name or a UDID. Leave simulator out for a Mac app.

Airplane mode in a simulator app launched with relaunch_app acts like a device's, within about 2 seconds: requests fail with NSURLErrorNotConnectedToInternet (-1009), NWPathMonitor reports an unsatisfied path and calls its handler, and SCNetworkReachability reports no network. The app also gets an in-app notification "LagsmithNetworkDidChange" (userInfo["offline"]: Bool).

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_targetsB

List running simulators and the apps installed on them, running Mac apps, the presets, and the current rules.

statusB

Show every rule, what it's doing, and whether Lagsmith's proxy is running.

set_networkA

Slow down or break one app's network, and only that app's. Creates the rule if needed and turns it on. Combine a preset with exact values or a failure mode.

reset_networkA

Put an app back to full speed with no failures, host limits or endpoint rules. It stays watched, so its requests still show.

stop_watchingA

Turn off an app's rule. Its traffic goes back to normal and stops being watched.

relaunch_appA

Quit and reopen a simulator app with request monitoring, so every connection it makes goes through its rule and its requests are recorded. Do this after the first set_network for an app that was already running.

get_requestsA

A simulator app's recent HTTP requests, newest first: method, URL, status, errors, time, and optionally bodies. Needs the app to have been launched with request monitoring (relaunch_app).

fail_endpointA

Make requests to one endpoint fail inside a simulator app while the rest of the app works.

mock_endpointB

Answer requests to one endpoint in a simulator app with a made-up response, without reaching the server.

clear_endpointsB

Remove an app's endpoint failures and mocks: all of them, or those for one pattern.

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 10 tools

Disambiguation4/5

Most tools have clearly distinct scopes: whole-app network shaping, endpoint-specific failure/mocking, request inspection, and lifecycle controls. The main overlap is between list_targets and status, since both expose current rules; reset_network, stop_watching, and clear_endpoints are also related but descriptions distinguish them.

Naming Consistency4/5

The set mostly follows a snake_case verb_noun convention such as set_network, fail_endpoint, and clear_endpoints. The only notable deviation is the bare noun status, which breaks the pattern slightly but remains clear.

Tool Count5/5

Ten tools is well scoped for an app network-conditioning and request-inspection server. Each tool supports a distinct step in the workflow: discovery, rule lifecycle, endpoint behavior, relaunching, and request review.

Completeness4/5

The surface covers the core lifecycle: discovering targets, applying/resetting/stopping network rules, failing or mocking endpoints, clearing endpoint rules, relaunching for monitoring, and fetching requests. Minor gaps exist around bulk rule management and explicit host-limit/preset editing, but the main workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues