thermoslop
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_thermostatsA | List paired thermostats: alias, name, house, and whether the last reading succeeded. |
| get_statusA | Current temperature, humidity, HVAC mode and action, setpoints, comfort setting
(home/away/sleep, or 'hold' for a manual hold) and remote sensors, in each thermostat's
own units ( |
| set_temperatureA | Set an absolute setpoint, in °F unless |
| adjust_temperatureA | Raise or lower the setpoint by |
| set_modeA | Set the HVAC mode. 'off' is disabled on this server. |
| set_comfortA | Hold a comfort setting until resume_schedule. With |
| resume_scheduleA | Clear holds (setpoint or comfort) and return to the thermostat's schedule. With |
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 7 tools
Each tool maps to a distinct action: listing devices, reading status, absolute setpoint, relative adjustment, mode, comfort preset, and clearing holds. set_temperature vs adjust_temperature overlap conceptually but the descriptions make the absolute-vs-delta distinction explicit, and get_status's no-argument mode slightly overlaps list_thermostats but reports different data.
All seven tools follow a consistent snake_case verb_noun or verb_target pattern (list_thermostats, get_status, set_temperature, adjust_temperature, set_mode, set_comfort, resume_schedule). The set_/adjust_/resume_ verb families are used meaningfully and predictably.
Seven tools is well-scoped for a thermostat control server, with each tool earning its place. There is no redundancy and no obvious filler.
Core lifecycle is covered: discovery, status, absolute and relative setpoint control, mode changes, comfort presets, and schedule resumption. Minor gaps exist (no fan control, no unpair/remove thermostat, no sensor-specific operations), but agents can accomplish the primary workflows.