peeko
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
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 |
|---|---|
| list_ios_simulatorsA | List all booted iOS Simulators (macOS only) |
| screenshot_iosA | Take a screenshot of an iOS Simulator screen. Returns a PNG image. (macOS only) |
| info_iosA | Get detailed info about an iOS Simulator (name, OS version, screen size). (macOS only) |
| list_android_emulatorsB | List all connected Android devices and emulators |
| screenshot_androidB | Take a screenshot of an Android device/emulator screen. Returns a PNG image. |
| info_androidA | Get detailed info about an Android device/emulator (name, OS version, screen size) |
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 6 tools
Each tool targets a specific platform (Android or iOS) and action (info, list, screenshot), with no overlap or ambiguity.
All tools follow a consistent pattern: <action>_<platform> (e.g., info_android, list_ios_simulators), using lowercase with underscores.
Six tools cover the core operations for two platforms (listing, info, screenshots) without excess or deficiency.
The tool surface is complete for the stated purpose of retrieving device/simulator info, listing, and screenshots; no obvious gaps.