Skip to main content
Glama
lenvolk
by lenvolk

set_state

Control LIFX smart lights by adjusting power, color, brightness, and infrared settings for selected lights.

Instructions

Set the state of lights

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesLIFX API token
selectorNoSelector for filtering lights (default: 'all')
powerNoPower state
colorNoColor string
brightnessNoBrightness (0.0 to 1.0)
durationNoDuration in seconds
infraredNoInfrared brightness (0.0 to 1.0)
fastNoFast mode (skip confirmation)

Implementation Reference

  • The main handler logic for the 'set_state' tool. It destructures the arguments, filters out undefined state parameters (power, color, brightness, duration, infrared, fast), makes a PUT request to the LIFX API endpoint `/lights/{selector}/state` using the makeLIFXRequest helper, and returns a success message with the API response.
    case "set_state": {
      const { token, selector = "all", ...stateParams } = args as {
        token: string;
        selector?: string;
        power?: string;
        color?: string;
        brightness?: number;
        duration?: number;
        infrared?: number;
        fast?: boolean;
      };
    
      const body = Object.fromEntries(
        Object.entries(stateParams).filter(([_, value]) => value !== undefined)
      );
    
      const result = await makeLIFXRequest(`/lights/${selector}/state`, {
        method: "PUT",
        body,
        token,
      });
    
      return {
        content: [
          {
            type: "text",
            text: `State updated successfully for selector "${selector}". ${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • src/index.ts:154-171 (registration)
    Registration of the 'set_state' tool in the ListTools response, including its description and full inputSchema (JSON Schema) defining parameters, types, descriptions, and required fields.
    {
      name: "set_state",
      description: "Set the state of lights",
      inputSchema: {
        type: "object",
        properties: {
          token: { type: "string", description: "LIFX API token" },
          selector: { type: "string", description: "Selector for filtering lights (default: 'all')" },
          power: { type: "string", enum: ["on", "off"], description: "Power state" },
          color: { type: "string", description: "Color string" },
          brightness: { type: "number", minimum: 0, maximum: 1, description: "Brightness (0.0 to 1.0)" },
          duration: { type: "number", minimum: 0, description: "Duration in seconds" },
          infrared: { type: "number", minimum: 0, maximum: 1, description: "Infrared brightness (0.0 to 1.0)" },
          fast: { type: "boolean", description: "Fast mode (skip confirmation)" },
        },
        required: ["token"],
      },
    },
  • The input schema (JSON Schema) for the set_state tool, specifying validation rules for all parameters.
      inputSchema: {
        type: "object",
        properties: {
          token: { type: "string", description: "LIFX API token" },
          selector: { type: "string", description: "Selector for filtering lights (default: 'all')" },
          power: { type: "string", enum: ["on", "off"], description: "Power state" },
          color: { type: "string", description: "Color string" },
          brightness: { type: "number", minimum: 0, maximum: 1, description: "Brightness (0.0 to 1.0)" },
          duration: { type: "number", minimum: 0, description: "Duration in seconds" },
          infrared: { type: "number", minimum: 0, maximum: 1, description: "Infrared brightness (0.0 to 1.0)" },
          fast: { type: "boolean", description: "Fast mode (skip confirmation)" },
        },
        required: ["token"],
      },
    },
  • Core helper function makeLIFXRequest used by the set_state handler to perform authenticated HTTP requests to the LIFX API, handling headers, JSON body, error checking, and response parsing.
    async function makeLIFXRequest(
      endpoint: string,
      options: {
        method?: string;
        body?: any;
        token: string;
      }
    ): Promise<any> {
      const { method = "GET", body, token } = options;
      
      const url = `${LIFX_API_BASE}${endpoint}`;
      const headers: Record<string, string> = {
        "Authorization": `Bearer ${token}`,
        "User-Agent": USER_AGENT,
      };
    
      if (body && (method === "POST" || method === "PUT")) {
        headers["Content-Type"] = "application/json";
      }
    
      try {
        const response = await fetch(url, {
          method,
          headers,
          body: body ? JSON.stringify(body) : undefined,
        });
    
        if (!response.ok) {
          const errorText = await response.text();
          throw new Error(`LIFX API error: ${response.status} ${response.statusText} - ${errorText}`);
        }
    
        // Some endpoints return empty responses
        const contentType = response.headers.get("content-type");
        if (contentType?.includes("application/json")) {
          return await response.json();
        }
        
        return await response.text();
      } catch (error) {
        throw new Error(`Failed to make LIFX API request: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Set the state of lights' implies a mutation operation, but it does not mention permissions, side effects (e.g., whether changes are reversible), rate limits, or response behavior. This is inadequate for a tool with multiple parameters and no output schema.

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 a single, efficient sentence with no wasted words, making it easy to parse. It is front-loaded with the core action, though it could benefit from more detail given the tool's complexity.

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

Completeness2/5

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

Given the tool's complexity (8 parameters, mutation operation) and lack of annotations and output schema, the description is incomplete. It does not address behavioral aspects, usage context, or return values, leaving significant gaps for an agent to understand how to invoke it effectively.

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 8 parameters. The description adds no additional meaning beyond implying that parameters like 'power', 'color', and 'brightness' are part of the state being set. With high schema coverage, the baseline score of 3 is appropriate as the description does not compensate but does not detract.

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 'Set the state of lights' clearly states the verb ('Set') and resource ('lights'), making the purpose understandable. However, it does not differentiate from sibling tools like 'toggle_power' or 'activate_scene', which also modify light states, leaving some ambiguity about when to choose this tool over others.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It lacks context about prerequisites (e.g., needing a token), exclusions, or comparisons to siblings like 'toggle_power' for simple on/off or 'activate_scene' for preset configurations, leaving the agent without usage direction.

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/lenvolk/mcp-lifx'

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