Skip to main content
Glama

Check ThermoWorks Auth Status

thermoworks_check_auth
Read-onlyIdempotent

Verify authentication status and token expiry for ThermoWorks Cloud integration to enable real-time BBQ temperature monitoring and cooking guidance.

Instructions

Check if you're currently authenticated with ThermoWorks Cloud.

Returns: Authentication status and token expiry time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the thermoworks_check_auth tool. It checks the ThermoWorks client's authentication status and returns appropriate markdown content and structured data indicating whether the user is authenticated, along with user ID and token expiry information.
    async (_params: CheckAuthStatusInput) => {
      const client = getThermoWorksClient();
      const isAuth = client.isAuthenticated();
      const authInfo = client.getAuthInfo();
    
      if (!isAuth) {
        return {
          content: [
            {
              type: "text",
              text: `## 🔒 Not Authenticated\n\nUse \`thermoworks_authenticate\` to connect to ThermoWorks Cloud.`,
            },
          ],
          structuredContent: { authenticated: false },
        };
      }
    
      const output = {
        authenticated: true,
        userId: authInfo.userId,
        tokenExpiry: authInfo.tokenExpiry?.toISOString(),
        tokenValid: authInfo.tokenExpiry ? authInfo.tokenExpiry > new Date() : false,
      };
    
      return {
        content: [
          {
            type: "text",
            text: `## ✅ Authenticated\n\n**User ID:** ${authInfo.userId}\n**Token Expires:** ${authInfo.tokenExpiry?.toLocaleString()}`,
          },
        ],
        structuredContent: output,
      };
    }
  • Zod schema definition for the tool's input parameters. This schema defines an empty object (no required parameters) with strict mode.
    /**
     * Schema for checking authentication status
     */
    export const CheckAuthStatusSchema = z.object({}).strict();
    
    export type CheckAuthStatusInput = z.infer<typeof CheckAuthStatusSchema>;
  • src/index.ts:1074-1124 (registration)
    The server.registerTool call that registers the thermoworks_check_auth tool with the MCP server, specifying its metadata, input schema, annotations, and inline handler function.
    server.registerTool(
      "thermoworks_check_auth",
      {
        title: "Check ThermoWorks Auth Status",
        description: `Check if you're currently authenticated with ThermoWorks Cloud.
    
    Returns:
      Authentication status and token expiry time.`,
        inputSchema: CheckAuthStatusSchema,
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false,
        },
      },
      async (_params: CheckAuthStatusInput) => {
        const client = getThermoWorksClient();
        const isAuth = client.isAuthenticated();
        const authInfo = client.getAuthInfo();
    
        if (!isAuth) {
          return {
            content: [
              {
                type: "text",
                text: `## 🔒 Not Authenticated\n\nUse \`thermoworks_authenticate\` to connect to ThermoWorks Cloud.`,
              },
            ],
            structuredContent: { authenticated: false },
          };
        }
    
        const output = {
          authenticated: true,
          userId: authInfo.userId,
          tokenExpiry: authInfo.tokenExpiry?.toISOString(),
          tokenValid: authInfo.tokenExpiry ? authInfo.tokenExpiry > new Date() : false,
        };
    
        return {
          content: [
            {
              type: "text",
              text: `## ✅ Authenticated\n\n**User ID:** ${authInfo.userId}\n**Token Expires:** ${authInfo.tokenExpiry?.toLocaleString()}`,
            },
          ],
          structuredContent: output,
        };
      }
    );
Behavior4/5

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

Annotations already provide key behavioral hints (readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false). The description adds value by specifying what the tool returns ('Authentication status and token expiry time'), which isn't covered by annotations. It doesn't contradict annotations, as 'checking' aligns with read-only and non-destructive behavior.

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

Conciseness5/5

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

The description is highly concise and well-structured: the first sentence directly states the purpose, and the second clarifies the return values. Both sentences earn their place by providing essential information without redundancy or fluff, making it easy for an agent to parse quickly.

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 simplicity (0 parameters, no output schema, rich annotations), the description is adequately complete. It explains what the tool does and what it returns, covering the core functionality. However, it could slightly enhance completeness by mentioning typical use cases (e.g., pre-operation verification) or error scenarios, though this isn't critical for such a straightforward tool.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100% (though trivial due to no parameters). The description doesn't need to add parameter details, so it appropriately focuses on output semantics. This meets the baseline for zero-parameter tools, as there's no schema burden to compensate for.

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

Purpose4/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: 'Check if you're currently authenticated with ThermoWorks Cloud.' It specifies the verb ('Check') and resource ('ThermoWorks Cloud authentication status'), making the intent unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'thermoworks_authenticate' beyond the obvious difference in action (checking vs. establishing authentication).

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 context by focusing on authentication status, suggesting it should be used to verify connectivity before performing other ThermoWorks operations. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'thermoworks_authenticate' for initial setup) or any exclusions, leaving the agent to infer optimal usage scenarios.

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