windows-power
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WINDOWS_POWER_POWERSHELL | No | Path to the Windows PowerShell executable. Defaults to /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe. Set when Windows is mounted somewhere else. | /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe |
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 |
|---|---|
| get_shutdown_statusA | Read the active Windows shutdown schedule and exact remaining time. |
| schedule_shutdownB | Schedule a one-time Windows shutdown. Replaces an existing Windows Power MCP shutdown. Forced app closing can lose unsaved work. |
| postpone_shutdownB | Move the active Windows shutdown later or earlier by a signed number of minutes. |
| cancel_shutdownA | Cancel the shutdown managed by Windows Power MCP. |
| shutdown_nowA | Force Windows to shut down after five seconds. This can lose unsaved work and requires an exact confirmation string. |
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 covers a distinct aspect of shutdown management: status, scheduling, postponing, canceling, and immediate shutdown. There is no overlap or ambiguity between tool purposes.
Most tools follow a clear verb_noun pattern: get_shutdown_status, schedule_shutdown, postpone_shutdown, cancel_shutdown. shutdown_now is the only slight deviation, but it remains immediately understandable and consistent in style.
Five tools is well-scoped for a shutdown management server. Each tool fulfills a necessary role without redundancy or bloat.
The tool set covers the full shutdown lifecycle: read status, schedule, modify, cancel, and execute immediately. There are no obvious missing operations for the stated domain.