JevSim
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPESAFE_API_KEY | No | API key for TypeSafe, used for semantic selection. Not required for exact-identifier workflows. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jevsim_statusA | Check backend connection, supported capabilities, iOS simulators or Android devices, and credential presence. Defaults to iOS. No secrets returned. |
| jevsim_inspectA | Read accessibility state for an explicit booted iOS simulator or connected Android device. Use simulatorId for iOS; platform android and deviceId for Android. Android first use starts an Appium session. Returned UI text may be private. |
| jevsim_run_stepsA | Execute up to 10 caller-planned tap/type/scroll/wait/assert steps within 60 seconds. Every action needs a deterministic expected outcome. Reserve the simulator or Android device for this call; do not use another UI tool concurrently. Returns partial progress and stops on ambiguity or failure. Never automatically replay uncertain actions. |
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 3 tools
Each tool has a clearly distinct purpose: status checks environment and credentials, inspect reads the current UI state, and run_steps executes user-defined interaction steps. There is no meaningful overlap that would cause an agent to select the wrong tool.
All tools share the consistent jevsim_ prefix and use clear, readable snake_case names. The only minor deviation is jevsim_status being a noun rather than a verb_phrase like jevsim_inspect and jevsim_run_steps, but the pattern is still easy to predict.
Three tools is well-scoped for this server's apparent purpose: check environment, inspect UI state, and run UI interaction steps. Each tool earns its place and there is no redundancy or bloat.
The tool set covers the core workflow of connecting, inspecting, and interacting with a simulator or device in a structured way. Minor gaps exist—such as no explicit screenshot or app-launch tool—but agents can likely work around these using the provided inspect and run_steps capabilities.