Skip to main content
Glama
kaeljune

Fibaro HC3 MCP Server

by kaeljune

fibaro_get_devices

Retrieve all connected smart home devices from your Fibaro Home Center 3 system to view and manage your home automation setup.

Instructions

Get all devices from Fibaro HC3

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'fibaro_get_devices' that checks connection, fetches devices via FibaroClient, and returns formatted list.
    case 'fibaro_get_devices': {
      if (!this.fibaroClient) {
        throw new Error('Not connected to Fibaro HC3. Please check your configuration and restart the MCP server.');
      }
      const devices = await this.fibaroClient.getDevices();
      return {
        content: [
          {
            type: 'text',
            text: `Found ${devices.length} devices:\n\n${devices
              .map(d => `ID: ${d.id} - ${d.name} (${d.type}) - Room: ${d.roomID}`)
              .join('\n')}`,
          },
        ],
      };
    }
  • Input schema for fibaro_get_devices tool: empty object (no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • src/index.ts:112-119 (registration)
    Registration of the fibaro_get_devices tool in the listTools response.
    {
      name: 'fibaro_get_devices',
      description: 'Get all devices from Fibaro HC3',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • FibaroClient.getDevices() method that makes API call to /api/devices and returns device list.
    async getDevices(): Promise<Device[]> {
      try {
        const response = await this.client.get('/api/devices');
        return response.data;
      } catch (error) {
        throw new Error(`Failed to get devices: ${error}`);
      }
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It lacks details on behavior such as pagination, rate limits, error handling, or what 'all devices' includes (e.g., status, metadata). This leaves significant gaps for an agent to understand operational traits.

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 front-loads the key action and resource, making it easy to parse quickly.

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 no annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't explain return values (e.g., device list format), error cases, or how it fits into the broader toolset, making it inadequate for full contextual understanding.

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 0 parameters with 100% schema coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, but it doesn't compensate for any gaps since there are none.

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 all devices') and resource ('from Fibaro HC3'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'fibaro_get_device' (singular) or 'fibaro_get_rooms', leaving room for confusion about scope.

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. For example, it doesn't specify if this should be used for bulk retrieval versus 'fibaro_get_device' for single devices, or mention prerequisites like authentication or system state.

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