Skip to main content
Glama
lsemenenko

OpenHue MCP Server

by lsemenenko

get-scenes

Retrieve and list all Philips Hue scenes or filter by room for specific details using the OpenHue MCP Server. Simplify light scene management.

Instructions

List all scenes or get details for specific scenes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomNoOptional room name to filter scenes

Implementation Reference

  • Handler for the 'get-scenes' tool: constructs OpenHue CLI command 'get scene' optionally with --room filter, executes it, and returns the JSON output as text content.
    case "get-scenes": {
      let command = "get scene";
      if (args?.room) {
        command += ` --room "${args.room}"`;
      }
      command += " --json";
      const result = await executeHueCommand(command);
      return {
        content: [
          {
            type: "text",
            text: result,
          },
        ],
      };
    }
  • src/index.ts:182-194 (registration)
    Registration of the 'get-scenes' tool in the ListToolsRequestHandler response, defining its name, description, and input schema.
    {
      name: "get-scenes",
      description: "List all scenes or get details for specific scenes",
      inputSchema: {
        type: "object",
        properties: {
          room: {
            type: "string",
            description: "Optional room name to filter scenes",
          },
        },
      },
    },
  • Helper function used by get-scenes handler to execute OpenHue Docker CLI commands and return stdout.
    async function executeHueCommand(command: string): Promise<string> {
      try {
        const { stdout, stderr } = await execAsync(buildDockerCommand(command));
        if (stderr) {
          console.error("Command error:", stderr);
          throw new Error(stderr);
        }
        return stdout;
      } catch (error) {
        console.error("Execution error:", error);
        throw error;
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists or gets details, implying a read-only operation, but doesn't address permissions, rate limits, pagination, or error handling. The description is minimal and lacks behavioral context beyond the basic purpose.

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 extremely concise and front-loaded, consisting of a single sentence that efficiently conveys the core functionality. There is no wasted language, and it immediately communicates the tool's dual modes of operation.

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 lack of annotations and output schema, the description is incomplete for a tool with potential complexity (e.g., listing vs. detailing scenes, filtering). It doesn't explain return values, error conditions, or behavioral nuances, leaving significant gaps for the agent to navigate.

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?

The input schema has 100% description coverage, with the single parameter 'room' documented as 'Optional room name to filter scenes'. The description adds no additional meaning beyond this, such as format examples or filtering logic, so it meets the baseline for high schema coverage without compensating value.

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 with specific verbs ('List all scenes' and 'get details for specific scenes') and identifies the resource ('scenes'). It distinguishes between two modes of operation, though it doesn't explicitly differentiate from sibling tools like 'get-lights' or 'get-rooms'.

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 doesn't mention sibling tools like 'get-lights' or 'get-rooms', nor does it specify contexts where this tool is preferred or excluded, leaving the agent to infer usage based on the purpose alone.

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

Related 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/lsemenenko/openhue-mcp-server'

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