displaybuddy-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| displaybuddy_statusA | Get a quick overview of all connected displays with their current brightness, contrast, volume, and input source. Always call this first to discover display names before using other tools. |
| displaybuddy_listA | List all connected displays with full details including UUID, type, control mode, max values, and capability flags. |
| displaybuddy_getB | Get current properties of a specific display. |
| displaybuddy_setA | Set display properties like brightness, contrast, volume, input source, or rotation. Can target a specific display by name or all displays at once. |
| displaybuddy_preset_listA | List all saved display presets. |
| displaybuddy_preset_activateB | Activate a saved display preset by name. |
| displaybuddy_schedule_listA | List all display automation schedules with their trigger type, preset, and enabled status. |
| displaybuddy_schedule_toggleB | Enable or disable a display automation schedule. |
| displaybuddy_syncA | Manage display sync. Sync makes all displays follow one source display's brightness, contrast, and volume. Can check status, enable with a source display, or disable. |
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 9 tools
Every tool has a clearly distinct purpose: get vs list, set vs status, preset actions, schedule actions, sync. No overlapping functionality, agents can easily select the correct tool.
All tools follow the pattern 'displaybuddy_<verb>' with consistent lowercase snake_case. Verbs like get, list, activate, set, status, sync are used predictably.
9 tools is well-scoped for display management. Covers discovery, property setting, presets, schedules, and sync without unnecessary extras.
Covers core operations well, but lacks tools to create or delete presets and schedules. Since the server can activate/toggle existing ones, the gap is minor.