Grok Gadgets Gateway
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gadgets_list_devicesB | Discover devices, capability schemas, availability and simulation labels. |
| gadgets_get_stateB | Read reported state and freshness; physical effect is not verified. |
| gadgets_commandB | Request a device action with a stable retry ID; distinguish accepted from executed. |
| gadgets_command_statusC | Read execution acknowledgement; timed_out/unconfirmed require human recovery. |
| gadgets_read_eventsC | Read bounded ordered event history; null cursor recovers explicit history loss. |
| gadgets_diagnosticsA | Get an allowlisted support report without tokens, state, arguments or raw errors. |
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 6 tools
Each tool targets a distinct stage of the device interaction lifecycle: discovery, state read, command dispatch, command acknowledgement, event history, and diagnostics. The descriptions explicitly separate reported state from execution acknowledgement and command request from command status.
All names use a consistent snake_case pattern with the gadgets_ prefix and a predictable verb/noun or action-noun structure. The slight noun form in gadgets_diagnostics does not break the overall convention.
Six tools is well-scoped for a device gateway: it covers discovery, inspection, control, execution tracking, history, and support without redundant or missing categories. Every tool has a clear role.
The set covers the core lifecycle from discovery through command acknowledgement and event history, with diagnostics for support. A minor gap is the absence of an explicit command cancellation or recovery operation, though status descriptions note human recovery for timed-out/unconfirmed cases.