Skip to main content
Glama
kaeljune

Fibaro HC3 MCP Server

by kaeljune

fibaro_get_scene

Retrieve a specific scene by its ID from Fibaro Home Center 3 to manage smart home automation sequences.

Instructions

Get specific scene by ID from Fibaro HC3

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesScene ID

Implementation Reference

  • MCP server handler for the fibaro_get_scene tool. Checks Fibaro connection, retrieves the specific scene using FibaroClient.getScene, formats and returns the scene details as text content.
    case 'fibaro_get_scene': {
      if (!this.fibaroClient) {
        throw new Error('Not connected to Fibaro HC3. Please check your configuration and restart the MCP server.');
      }
      const scene = await this.fibaroClient.getScene(args?.id as number);
      return {
        content: [
          {
            type: 'text',
            text: `Scene ${scene.id}:\nName: ${scene.name}\nRoom ID: ${scene.roomID}\nEnabled: ${scene.enabled}\nVisible: ${scene.visible}\nIs Lua: ${scene.isLua}`,
          },
        ],
      };
    }
  • src/index.ts:142-155 (registration)
    Registration of the fibaro_get_scene tool in the ListTools response, including name, description, and input schema requiring a scene ID.
    {
      name: 'fibaro_get_scene',
      description: 'Get specific scene by ID from Fibaro HC3',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Scene ID',
          },
        },
        required: ['id'],
      },
    },
  • TypeScript interface defining the structure of a Scene object, used as the return type for getScene.
    export interface Scene {
      id: number;
      name: string;
      roomID: number;
      enabled: boolean;
      visible: boolean;
      isLua: boolean;
    }
  • FibaroClient helper method that makes an HTTP GET request to the Fibaro API endpoint /api/scenes/{id} to fetch the specific scene data.
    async getScene(id: number): Promise<Scene> {
      try {
        const response = await this.client.get(`/api/scenes/${id}`);
        return response.data;
      } catch (error) {
        throw new Error(`Failed to get scene ${id}: ${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 it's a 'Get' operation, implying read-only, but doesn't clarify if it requires authentication, has rate limits, returns error handling details, or what the output format is. This leaves significant gaps for a tool with no annotation coverage.

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 zero waste. It's front-loaded with the core action and resource, making it appropriately sized and easy to parse.

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 (a read operation with no output schema and no annotations), the description is incomplete. It doesn't explain what information is returned (e.g., scene details, status), error conditions, or behavioral traits like permissions needed. This leaves the agent with insufficient context for reliable use.

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 'id' parameter clearly documented as 'Scene ID'. The description adds no additional meaning beyond this, such as explaining ID formats or constraints. Baseline 3 is appropriate since the schema does the heavy lifting.

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 action ('Get specific scene') and resource ('from Fibaro HC3'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'fibaro_get_scenes' (which likely lists scenes) or 'fibaro_get_device' (which gets devices), so it misses full sibling distinction.

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 when to choose 'fibaro_get_scene' over 'fibaro_get_scenes' or other sibling tools, nor does it specify prerequisites like needing a valid scene ID.

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