Skip to main content
Glama

Get Live Temperature Readings

thermoworks_get_live_readings
Read-only

Retrieve real-time temperature data from ThermoWorks BBQ probes to monitor your cook. Specify a device or get readings from all connected probes.

Instructions

Get current temperature readings from your ThermoWorks devices.

Requires authentication first via thermoworks_authenticate.

Args:

  • device_serial: Serial number of specific device (optional, defaults to all devices)

  • response_format: 'markdown' or 'json'

Returns: Current probe temperatures, alarm settings, and timestamps.

Examples:

  • "What are my current temperatures?" -> Gets all device readings

  • "Show me the Signals readings" -> Specify device_serial

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_serialNoSerial number of specific device to query. If not provided, returns readings from all devices.
response_formatNoOutput formatmarkdown

Implementation Reference

  • Main handler function for thermoworks_get_live_readings tool. Fetches live temperature readings from authenticated ThermoWorks devices, handles specific device or all devices, supports JSON/markdown output, includes alarms and timestamps.
    async (params: GetLiveReadingsInput) => {
      try {
        const client = getThermoWorksClient();
    
        if (!client.isAuthenticated()) {
          return {
            isError: true,
            content: [
              {
                type: "text",
                text: "Not authenticated. Use `thermoworks_authenticate` first.",
              },
            ],
          };
        }
    
        let readings;
        if (params.device_serial) {
          const reading = await client.getDeviceReadings(params.device_serial);
          readings = reading ? [reading] : [];
        } else {
          readings = await client.getAllReadings();
        }
    
        if (readings.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "No readings available. Make sure your devices are powered on and connected.",
              },
            ],
          };
        }
    
        if (params.response_format === "json") {
          return {
            content: [{ type: "text", text: JSON.stringify(readings, null, 2) }],
            structuredContent: { readings },
          };
        }
    
        let markdown = `## 🌡️ Live Temperature Readings\n\n`;
        markdown += `*Updated: ${new Date().toLocaleString()}*\n\n`;
    
        for (const reading of readings) {
          markdown += `### ${reading.name} (${reading.serial})\n\n`;
    
          for (const [probeId, probe] of Object.entries(reading.probes)) {
            const alarmStr =
              probe.alarm_high || probe.alarm_low
                ? ` (Alarm: ${probe.alarm_low || "—"}–${probe.alarm_high || "—"}°${reading.unit})`
                : "";
    
            markdown += `- **${probe.name || `Probe ${probeId}`}:** ${probe.temp}°${reading.unit}${alarmStr}\n`;
          }
          markdown += "\n";
        }
    
        return {
          content: [{ type: "text", text: markdown }],
        };
      } catch (error) {
        const message = error instanceof Error ? error.message : "Failed to get readings";
        return {
          isError: true,
          content: [{ type: "text", text: `Error: ${message}` }],
        };
      }
    }
  • Zod input schema for the tool, defining device_serial (optional) and response_format parameters.
    export const GetLiveReadingsSchema = z
      .object({
        device_serial: z
          .string()
          .optional()
          .describe("Serial number of specific device to query. If not provided, returns readings from all devices."),
        response_format: ResponseFormatSchema.describe("Output format"),
      })
      .strict();
    
    export type GetLiveReadingsInput = z.infer<typeof GetLiveReadingsSchema>;
  • src/index.ts:1204-1229 (registration)
    Tool registration in the main MCP server using server.registerTool with title, description, input schema, and annotations.
    server.registerTool(
      "thermoworks_get_live_readings",
      {
        title: "Get Live Temperature Readings",
        description: `Get current temperature readings from your ThermoWorks devices.
    
    Requires authentication first via thermoworks_authenticate.
    
    Args:
      - device_serial: Serial number of specific device (optional, defaults to all devices)
      - response_format: 'markdown' or 'json'
    
    Returns:
      Current probe temperatures, alarm settings, and timestamps.
    
    Examples:
      - "What are my current temperatures?" -> Gets all device readings
      - "Show me the Signals readings" -> Specify device_serial`,
        inputSchema: GetLiveReadingsSchema,
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: false, // Readings change over time
          openWorldHint: true,
        },
      },
  • Key helper methods in ThermoWorksClient: getDeviceReadings and getAllReadings, which handle token refresh and fetch data from Firebase Realtime Database.
    async getDeviceReadings(serial: string): Promise<DeviceReading | null> {
      await this.ensureValidToken();
      return getDeviceReadings(this.idToken!, this.userId!, serial, this.useSmokeLegacy);
    }
    
    /**
     * Get all device readings
     */
    async getAllReadings(): Promise<DeviceReading[]> {
      await this.ensureValidToken();
      return getAllDeviceReadings(this.idToken!, this.userId!, this.useSmokeLegacy);
    }
  • Singleton factory for ThermoWorksClient used by the handler to get the authenticated client instance.
    export function getThermoWorksClient(useSmokeLegacy = false): ThermoWorksClient {
      if (!globalClient) {
        globalClient = new ThermoWorksClient(useSmokeLegacy);
      }
      return globalClient;
    }
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering safety and data scope. The description adds valuable context beyond this: it specifies the authentication requirement (not covered by annotations) and hints at return content (temperatures, alarms, timestamps). However, it doesn't mention rate limits or error behaviors, keeping it from a perfect score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections (Args, Returns, Examples), making it easy to scan. It's front-loaded with the core purpose and authentication requirement. However, the examples could be more concise, and some details (like restating parameter defaults) are slightly redundant given the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 parameters, no output schema, rich annotations), the description is largely complete. It covers purpose, prerequisites, parameters, and return content. The main gap is the lack of an output schema, but the description compensates by summarizing return values. It doesn't detail error cases or pagination, which is acceptable for this tool type.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with clear descriptions for both parameters (device_serial and response_format). The description adds minimal value beyond the schema: it restates that device_serial is optional and defaults to all devices, and lists the enum values for response_format, but doesn't provide additional semantic context like format differences or device identification tips.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get current temperature readings') and resource ('from your ThermoWorks devices'), distinguishing it from siblings like thermoworks_get_devices (which likely lists devices) and thermoworks_analyze_live (which likely analyzes readings). The verb 'Get' is precise and the scope is well-defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states 'Requires authentication first via thermoworks_authenticate', providing a clear prerequisite. It also distinguishes usage through examples: getting all device readings vs. specifying a device_serial, though it doesn't explicitly name alternatives like thermoworks_get_devices for device lists.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jweingardt12/bbq-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server