tempstick-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEMPSTICK_API_KEY | Yes | Your Temp Stick API key, found on the Account Page under the Developers tab at mytempstick.com |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sensorsA | List the Temp Stick sensors visible to your API key, with each sensor's latest temperature, humidity, battery level and offline status. |
| get_sensorA | Get the latest reading for one sensor: temperature (Celsius and Fahrenheit), humidity, last check-in, battery level and offline status. |
| get_freezer_statusA | One-call status check for a sensor (named for the classic freezer use case): latest reading, recent history summary and the account's alert definitions together, so the assistant can answer 'is it OK?' in a single call. |
| get_readings_historyA | Summarize a sensor's recent readings: count, min, max and average temperature (Fahrenheit), and the first and last reading times. |
| get_alertsA | List the alert definitions and state for the account (thresholds, delivery channels, whether triggered). |
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
Core tools (list_sensors, get_sensor, get_readings_history, get_alerts) target distinct resources, but get_freezer_status overlaps with three of them by bundling latest reading, history summary, and alerts. Its composite 'is it OK?' purpose is clearly described, so an agent can usually distinguish when to use it.
All tool names use a consistent snake_case verb_noun pattern: list_sensors, get_sensor, get_readings_history, get_alerts, and get_freezer_status. The singular/plural distinction in list_sensors and get_sensor is predictable and readable.
Five tools is well-scoped for a sensor monitoring integration. Each tool has a plausible role, and the set avoids both thinness and bloat.
The surface covers the main read-only workflows: listing sensors, fetching latest readings, summarizing history, checking alerts, and a one-call status helper. Minor gaps exist around alert state changes or sensor configuration, but these may be outside the API's intended scope.