Skip to main content
Glama

Analyze ThermoWorks Device Reading

bbq_analyze_device_reading
Read-onlyIdempotent

Analyzes temperature readings from ThermoWorks BBQ devices to provide cooking insights, detect stalls, estimate cook times, and offer protein-specific recommendations.

Instructions

Analyze temperature readings from a ThermoWorks device (Signals, Smoke, BlueDOT).

Simulates integration with ThermoWorks Cloud to provide analysis of multi-probe readings.

Args:

  • device_type: Type of ThermoWorks device ('Signals', 'Smoke', 'BlueDOT')

  • probe_readings: Array of probe readings with {probe_id, name, temperature}

  • protein_type: Type of protein being cooked (optional)

  • target_temp: Target temperature (optional)

  • response_format: 'markdown' or 'json'

Examples:

  • "Signals reading: Probe 1 at 165°F, Ambient at 250°F"

  • "Smoke shows 180°F on the meat probe"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_typeYesType of ThermoWorks device
probe_readingsYesTemperature readings from each probe
protein_typeNoType of protein being cooked (if known)
target_tempNoTarget temperature set on device
response_formatNoOutput formatmarkdown

Implementation Reference

  • The inline asynchronous handler function for the bbq_analyze_device_reading tool. It identifies the meat probe from readings, optionally performs temperature analysis if protein_type and target_temp are provided using analyzeTemperature, formats the output as markdown using formatDeviceReadingMarkdown or JSON, and handles errors.
    async (params: SimulateDeviceReadingInput) => {
      try {
        // Find the meat probe (not ambient)
        const meatProbe = params.probe_readings.find(
          (p) => !p.probe_id.toLowerCase().includes("ambient") && !p.name?.toLowerCase().includes("ambient")
        );
    
        let analysis: ReturnType<typeof analyzeTemperature> | undefined;
        if (meatProbe && params.protein_type && params.target_temp) {
          analysis = analyzeTemperature(
            meatProbe.temperature,
            params.target_temp,
            params.protein_type
          );
        }
    
        if (params.response_format === "json") {
          const output = {
            deviceType: params.device_type,
            probeReadings: params.probe_readings,
            proteinType: params.protein_type,
            targetTemp: params.target_temp,
            analysis: analysis
              ? {
                  currentTemp: analysis.currentTemp,
                  targetTemp: analysis.targetTemp,
                  percentComplete: analysis.percentComplete,
                  tempDelta: analysis.tempDelta,
                  recommendations: analysis.recommendations,
                }
              : null,
          };
    
          return {
            content: [{ type: "text", text: JSON.stringify(output, null, 2) }],
            structuredContent: output,
          };
        }
    
        const markdown = formatDeviceReadingMarkdown(
          params.device_type,
          params.probe_readings,
          analysis
        );
        return {
          content: [{ type: "text", text: markdown }],
        };
      } catch (error) {
        const message = error instanceof Error ? error.message : "Unknown error occurred";
        return {
          isError: true,
          content: [{ type: "text", text: `Error analyzing device reading: ${message}` }],
        };
      }
  • src/index.ts:824-905 (registration)
    Registration of the bbq_analyze_device_reading tool on the MCP server, including title, description, input schema (SimulateDeviceReadingSchema), annotations, and reference to the inline handler.
    server.registerTool(
      "bbq_analyze_device_reading",
      {
        title: "Analyze ThermoWorks Device Reading",
        description: `Analyze temperature readings from a ThermoWorks device (Signals, Smoke, BlueDOT).
    
    Simulates integration with ThermoWorks Cloud to provide analysis of multi-probe readings.
    
    Args:
      - device_type: Type of ThermoWorks device ('Signals', 'Smoke', 'BlueDOT')
      - probe_readings: Array of probe readings with {probe_id, name, temperature}
      - protein_type: Type of protein being cooked (optional)
      - target_temp: Target temperature (optional)
      - response_format: 'markdown' or 'json'
    
    Examples:
      - "Signals reading: Probe 1 at 165°F, Ambient at 250°F"
      - "Smoke shows 180°F on the meat probe"`,
        inputSchema: SimulateDeviceReadingSchema,
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false,
        },
      },
      async (params: SimulateDeviceReadingInput) => {
        try {
          // Find the meat probe (not ambient)
          const meatProbe = params.probe_readings.find(
            (p) => !p.probe_id.toLowerCase().includes("ambient") && !p.name?.toLowerCase().includes("ambient")
          );
    
          let analysis: ReturnType<typeof analyzeTemperature> | undefined;
          if (meatProbe && params.protein_type && params.target_temp) {
            analysis = analyzeTemperature(
              meatProbe.temperature,
              params.target_temp,
              params.protein_type
            );
          }
    
          if (params.response_format === "json") {
            const output = {
              deviceType: params.device_type,
              probeReadings: params.probe_readings,
              proteinType: params.protein_type,
              targetTemp: params.target_temp,
              analysis: analysis
                ? {
                    currentTemp: analysis.currentTemp,
                    targetTemp: analysis.targetTemp,
                    percentComplete: analysis.percentComplete,
                    tempDelta: analysis.tempDelta,
                    recommendations: analysis.recommendations,
                  }
                : null,
            };
    
            return {
              content: [{ type: "text", text: JSON.stringify(output, null, 2) }],
              structuredContent: output,
            };
          }
    
          const markdown = formatDeviceReadingMarkdown(
            params.device_type,
            params.probe_readings,
            analysis
          );
          return {
            content: [{ type: "text", text: markdown }],
          };
        } catch (error) {
          const message = error instanceof Error ? error.message : "Unknown error occurred";
          return {
            isError: true,
            content: [{ type: "text", text: `Error analyzing device reading: ${message}` }],
          };
        }
      }
    );
  • Zod schema definition for input validation of the bbq_analyze_device_reading tool, defining parameters like device_type, probe_readings array, optional protein_type, target_temp, and response_format.
    export const SimulateDeviceReadingSchema = z
      .object({
        device_type: z.enum(["Signals", "Smoke", "BlueDOT"]).describe("Type of ThermoWorks device"),
        probe_readings: z
          .array(
            z.object({
              probe_id: z.string().describe("Probe identifier (e.g., 'probe1', 'ambient')"),
              name: z.string().optional().describe("Custom name for this probe"),
              temperature: z.number().describe("Temperature reading"),
            })
          )
          .min(1)
          .max(4)
          .describe("Temperature readings from each probe"),
        protein_type: ProteinTypeSchema.optional().describe("Type of protein being cooked (if known)"),
        target_temp: z.number().optional().describe("Target temperature set on device"),
        response_format: ResponseFormatSchema.describe("Output format"),
      })
      .strict();
    
    export type SimulateDeviceReadingInput = z.infer<typeof SimulateDeviceReadingSchema>;
  • Helper function to format the device readings and optional temperature analysis into a readable Markdown output for the tool response.
    export function formatDeviceReadingMarkdown(
      deviceType: string,
      probeReadings: Array<{ probe_id: string; name?: string; temperature: number }>,
      analysis?: TemperatureAnalysis
    ): string {
      let output = `## 📱 ThermoWorks ${deviceType} Reading\n\n`;
    
      for (const probe of probeReadings) {
        const name = probe.name || probe.probe_id;
        output += `**${name}:** ${probe.temperature}°F\n`;
      }
    
      if (analysis) {
        output += `\n---\n\n`;
        output += formatTemperatureAnalysisMarkdown(analysis);
      }
    
      return output;
    }
Behavior3/5

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

Annotations already indicate the tool is read-only, non-destructive, and idempotent. The description adds context by stating it 'simulates integration with ThermoWorks Cloud,' which suggests it's a mock or test tool rather than a live API call. However, it does not disclose rate limits, authentication needs, or specific behavioral traits beyond what annotations provide.

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 a clear purpose statement, parameter list, and examples. It is appropriately sized, but the 'Args' section slightly duplicates schema information. Every sentence adds value, such as the simulation note and examples, making it efficient overall.

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

Completeness3/5

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

Given the tool's complexity (5 parameters, 100% schema coverage, annotations provided, no output schema), the description is adequate but has gaps. It explains the tool's purpose and simulation aspect but does not detail the analysis output (e.g., what insights are provided) or how it differs from sibling tools, leaving room for improvement in contextual guidance.

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%, so the schema fully documents all parameters. The description lists parameters in an 'Args' section but does not add meaningful semantics beyond the schema (e.g., it repeats 'device_type' and 'probe_readings' without extra context). The examples illustrate usage but do not clarify parameter meanings further.

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 tool's purpose: 'Analyze temperature readings from a ThermoWorks device (Signals, Smoke, BlueDOT).' It specifies the verb ('analyze'), resource ('temperature readings'), and device types, distinguishing it from siblings like 'bbq_analyze_temperature' (generic) or 'thermoworks_analyze_live' (live data).

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

Usage Guidelines3/5

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

The description implies usage for analyzing multi-probe readings from ThermoWorks devices, but does not explicitly state when to use this tool versus alternatives like 'thermoworks_analyze_live' (for live data) or 'bbq_analyze_temperature' (generic analysis). It mentions simulation of ThermoWorks Cloud integration, which provides some context but lacks clear exclusions or comparisons.

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