DeviceDeck
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVICE_DECK_HOME | No | Override the local data directory. Local data defaults to `~/.local/share/device-deck/inventory.sqlite` (outside this repo). Can also be set with `device-deck --home /private/path`. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| device_deck_list_devicesA | List registered device identities, LAN/remote/USB endpoints, credential references and timestamped observations. Does not probe devices or retrieve secrets. Limit 1..100, offset >= 0. |
| device_deck_get_deviceA | Read one device and its connection/credential metadata and saved observations. A saved status is historical, not proof the device is currently online. |
| device_deck_connection_planA | Return a connection command and human pairing/login prerequisites for one registered endpoint. Does not execute the command, retrieve a password, pair a phone or modify network settings. |
| device_deck_probe_deviceA | Run a fixed read-only probe against one registered SSH, paired ADB, trusted iOS USB or existing WDA endpoint. Saves a local observation and audit event. Never executes arbitrary shell/UI commands or performs pairing. Missing fields remain unknown. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| inventory_resource |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: list devices vs. read one device, plan a connection without executing it, and run a fixed read-only probe. The descriptions explicitly clarify boundaries, especially between connection_plan and probe_device.
All tools share the device_deck_ prefix, and most follow a verb_noun pattern (list_devices, get_device, probe_device). connection_plan is a minor deviation as a noun phrase rather than a verb-led name.
Four tools is well-scoped for a focused device registry/connection/probing server. Each tool covers a distinct operation without redundancy.
The set covers listing, reading, connection planning, and probing, but there are no tools to register, update, or remove devices or credentials. This is a notable lifecycle gap for a device management server, though read-only workflows are covered.