SleepBlocker MCP
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_sleep_preventionC | Start preventing system sleep with specified mode and duration |
| stop_sleep_preventionB | Stop active sleep prevention |
| get_sleep_statusA | Get current sleep prevention status and remaining time |
| list_sleep_modesA | List all available sleep prevention modes with descriptions |
| set_duration_presetB | Set duration using preset values (30min, 1hr, 2hr, 4hr, indefinite) |
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 5 tools
Each tool has a clearly distinct purpose: status check, listing modes, setting presets, starting, and stopping. No overlap between tools.
All tool names follow a consistent verb_noun pattern (e.g., get_sleep_status, start_sleep_prevention) using snake_case throughout.
5 tools is well-scoped for a sleep prevention utility, covering core actions without excess or deficiency.
The tool set covers the full lifecycle: start, stop, check status, list modes, and set duration. No obvious gaps in functionality.