ntdrive
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| con_screenshotA | Save a PNG of the VM console and return its path (base64 on request). |
| file_pushA | Copy a file, directory or glob from the host into the guest and verify it. |
| file_pullA | Copy a file from the guest to the host. |
| kd_setup_hostB | Prepare the host side of the kd transport: serial adds the named-pipe COM port to the vmx (VM must be off), net reports the one-time firewall step. |
| kd_setup_guestA | Enable kernel debugging in the guest with bcdedit over SSH (serial or KDNET per kd_transport) and store the KDNET port and key in vms.yaml. |
| kd_attachB | Start kd.exe for the VM and (by default) wait until the target connects. |
| kd_detachA | Resume the target if needed and stop kd.exe. |
| kd_breakB | Break into the running target and wait for the kd> prompt. |
| kd_goD | Resume the target (g). |
| kd_execB | Run one or more debugger commands at the kd> prompt and return each command's output. |
| kd_wait_eventC | Wait until the running target stops (bugcheck, breakpoint, ...) or the timeout expires. |
| kd_stateC | Debugger state, transport, target info, last event and log path. |
| kd_log_tailC | Last bytes of the kd.exe transcript. |
| snap_listB | Snapshot tree of a VM plus the current snapshot and stored metadata. |
| snap_takeA | Take a snapshot (memory included while running) and record description and kd state. |
| snap_revertA | Revert to a snapshot: detach kd, revert, start, reattach kd, reopen terminals. |
| snap_deleteA | Delete a snapshot (and optionally its children). Needs confirm=true. |
| sys_stateA | VM power, debugger state, terminal sessions and last events in one answer. |
| sys_healthA | Check binaries, config and backend capabilities, then probe every VM: power, guest SSH port and the debugger transport on the host. Run this first. |
| term_openB | Open a real-time PTY session (SSH) on the guest and return its session_id. |
| term_sendB | Type text and/or a burst of keys into a session. Tokens: {enter} {tab} {esc} {ctrl+c} {up}. |
| term_readC | Read new output (delta), wait for a regex (until), or render the screen (mode=screen). |
| term_execB | Run one command in the session and return only its output and exit code. |
| term_resizeD | Resize the PTY. |
| term_closeC | Close a session. |
| term_listC | List terminal sessions and their state. |
| vm_listA | List registered VMs with power, debugger and terminal state. |
| vm_stateB | Power, debugger and terminal state of one VM. |
| vm_startC | Power on (or resume) a VM without the GUI by default. |
| vm_stopA | Shut the guest down (soft) or cut power (hard, needs confirm=true). |
| vm_rebootA | Reboot the guest (soft, hard or from the debugger) and bring kd and terminals back. |
| vm_suspendB | Suspend the VM to disk. |
| vm_resumeB | Resume a suspended VM (same as vm_start). |
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 33 tools
Most tools are clearly separated by domain prefix (kd_, con_, file_, term_, vm_, snap_, sys_), and within each domain the action is distinct. The only mild ambiguity is vm_resume vs vm_start (explicitly noted as same) and kd_go vs kd_detach (both resume the target, but one detaches kd.exe).
The naming follows a consistent verb_noun pattern with domain prefixes (kd_*, term_*, vm_*, snap_*, sys_*). Minor deviations: kd_setup_host/kd_setup_guest use setup as a verb, and con_screenshot is the only con_* tool, but overall the pattern is predictable.
33 tools is on the heavy side, but the server covers a broad domain (VM lifecycle, terminal sessions, kernel debugging, snapshots, file transfer, health checks). Each tool has a specific purpose, though some consolidation (e.g., vm_state vs vm_list vs sys_state) could reduce the count.
The tool surface is remarkably complete for the stated purpose: VM lifecycle (start/stop/reboot/suspend/resume), snapshots (list/take/revert/delete), terminal sessions (open/send/read/exec/resize/list/close), kernel debugging (setup/attach/break/go/exec/wait/state/log), file transfer (push/pull), and system health/state. No obvious dead ends.