Skip to main content
Glama
kaeljune

Fibaro HC3 MCP Server

by kaeljune

fibaro_run_scene

Execute a smart home scene on your Fibaro HC3 system by specifying the scene ID to automate lighting, devices, or routines.

Instructions

Run/start a scene

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesScene ID to run

Implementation Reference

  • MCP tool handler for fibaro_run_scene: extracts scene ID from arguments, calls FibaroClient.runScene, and returns success message.
    case 'fibaro_run_scene': {
      if (!this.fibaroClient) {
        throw new Error('Not connected to Fibaro HC3. Please check your configuration and restart the MCP server.');
      }
      const sceneId = args?.id as number;
      await this.fibaroClient.runScene(sceneId);
      return {
        content: [
          {
            type: 'text',
            text: `Successfully started scene ${sceneId}`,
          },
        ],
      };
    }
  • src/index.ts:301-313 (registration)
    Tool registration in ListTools response, including name, description, and input schema.
    {
      name: 'fibaro_run_scene',
      description: 'Run/start a scene',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Scene ID to run',
          },
        },
        required: ['id'],
      },
  • FibaroClient helper method that performs the HTTP POST to start the scene via Fibaro API.
    async runScene(id: number): Promise<void> {
      try {
        await this.client.post(`/api/scenes/${id}/action/start`, {
          args: []
        });
      } catch (error) {
        throw new Error(`Failed to run scene ${id}: ${error}`);
      }
    }
  • Input schema definition for the fibaro_run_scene tool.
    inputSchema: {
      type: 'object',
      properties: {
        id: {
          type: 'number',
          description: 'Scene ID to run',
        },
      },
      required: ['id'],
    },
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 action but does not explain what 'running a scene' does (e.g., triggers automation, affects devices), whether it requires specific permissions, or what the expected outcome or response might be. This leaves significant gaps in understanding the tool's 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 'Run/start a scene' is extremely concise—just three words—with zero wasted language. It is front-loaded and efficiently conveys the core action, though this brevity contributes to gaps in other dimensions.

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?

For a tool that performs an action (running a scene) with no annotations and no output schema, the description is insufficient. It lacks details on behavior, outcomes, error conditions, or how it interacts with sibling tools. Given the complexity implied by the action and the absence of structured data, more context is needed for completeness.

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 'id' documented as 'Scene ID to run'. The description does not add any additional meaning or context beyond this, such as how to obtain valid scene IDs or format requirements. Given the high schema coverage, a baseline score of 3 is appropriate.

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

Purpose3/5

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

The description 'Run/start a scene' clearly states the action (run/start) and target resource (a scene), which is adequate. However, it does not differentiate this tool from its sibling 'fibaro_stop_scene' or explain what 'running a scene' entails in this context, making it somewhat vague.

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 like 'fibaro_stop_scene' for stopping scenes or other device-specific tools (e.g., 'fibaro_turn_on_device'). There is no mention of prerequisites, such as needing a valid scene ID, or contextual cues for invocation.

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/kaeljune/fibaro-mcp-server'

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