Skip to main content
Glama
kaeljune

Fibaro HC3 MCP Server

by kaeljune

fibaro_get_scenes

Retrieve all configured scenes from your Fibaro Home Center 3 smart home system to manage automation routines and device interactions.

Instructions

Get all scenes from Fibaro HC3

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP server handler for fibaro_get_scenes tool: checks connection, calls fibaroClient.getScenes(), formats and returns the list of scenes.
    case 'fibaro_get_scenes': {
      if (!this.fibaroClient) {
        throw new Error('Not connected to Fibaro HC3. Please check your configuration and restart the MCP server.');
      }
      const scenes = await this.fibaroClient.getScenes();
      return {
        content: [
          {
            type: 'text',
            text: `Found ${scenes.length} scenes:\n\n${scenes
              .map(s => `ID: ${s.id} - ${s.name} - Room: ${s.roomID}`)
              .join('\n')}`,
          },
        ],
      };
    }
  • src/index.ts:135-141 (registration)
    Registration of the fibaro_get_scenes tool in the ListTools response, including name, description, and input schema (no parameters required).
      name: 'fibaro_get_scenes',
      description: 'Get all scenes from Fibaro HC3',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • TypeScript interface defining the structure of Scene objects used in fibaro_get_scenes.
    export interface Scene {
      id: number;
      name: string;
      roomID: number;
      enabled: boolean;
      visible: boolean;
      isLua: boolean;
  • FibaroClient.getScenes() method: performs HTTP GET to /api/scenes endpoint and returns the scenes data.
    async getScenes(): Promise<Scene[]> {
      try {
        const response = await this.client.get('/api/scenes');
        return response.data;
      } catch (error) {
        throw new Error(`Failed to get scenes: ${error}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation ('Get'), but doesn't describe what 'all scenes' means (e.g., pagination, filtering, format), whether authentication is required, or any rate limits. The description provides minimal behavioral context beyond the basic operation.

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. It's appropriately sized for a simple retrieval tool and gets straight to the point without unnecessary elaboration.

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

Completeness3/5

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

For a zero-parameter retrieval tool with no output schema, the description provides the basic operation but lacks important context. It doesn't explain what a 'scene' is in this system, what information is returned, or how this differs from the singular 'fibaro_get_scene' tool. The description is minimally adequate but leaves gaps in understanding the tool's full context.

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 zero parameters, and schema description coverage is 100% (empty schema). The description appropriately doesn't discuss parameters since there are none, and doesn't need to compensate for any schema gaps. This meets the baseline expectation for parameterless tools.

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 verb ('Get') and resource ('all scenes from Fibaro HC3'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'fibaro_get_scene' (singular) or explain how this differs from other retrieval tools in the set.

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?

No guidance is provided on when to use this tool versus alternatives like 'fibaro_get_scene' (singular scene retrieval) or 'fibaro_get_devices' (different resource type). The description only states what it does, not when it's appropriate.

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