Skip to main content
Glama
kaeljune

Fibaro HC3 MCP Server

by kaeljune

fibaro_get_device

Retrieve a specific smart home device by its ID from the Fibaro Home Center 3 system to access device details and status.

Instructions

Get specific device by ID from Fibaro HC3

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDevice ID

Implementation Reference

  • MCP tool handler for 'fibaro_get_device' that checks connection, calls FibaroClient.getDevice, and formats the response as text content.
    case 'fibaro_get_device': {
      if (!this.fibaroClient) {
        throw new Error('Not connected to Fibaro HC3. Please check your configuration and restart the MCP server.');
      }
      const device = await this.fibaroClient.getDevice(args?.id as number);
      return {
        content: [
          {
            type: 'text',
            text: `Device ${device.id}:\nName: ${device.name}\nType: ${device.type}\nRoom ID: ${device.roomID}\nEnabled: ${device.enabled}\nVisible: ${device.visible}\nProperties: ${JSON.stringify(device.properties, null, 2)}`,
          },
        ],
      };
    }
  • src/index.ts:120-133 (registration)
    Tool registration in ListTools handler, including name, description, and input schema requiring 'id'.
    {
      name: 'fibaro_get_device',
      description: 'Get specific device by ID from Fibaro HC3',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Device ID',
          },
        },
        required: ['id'],
      },
    },
  • TypeScript interface defining the Device structure returned by getDevice.
    export interface Device {
      id: number;
      name: string;
      type: string;
      roomID: number;
      enabled: boolean;
      visible: boolean;
      properties: Record<string, any>;
    }
  • Core implementation of device retrieval via HTTP GET to Fibaro API /api/devices/{id}, using Axios client.
    async getDevice(id: number): Promise<Device> {
      try {
        const response = await this.client.get(`/api/devices/${id}`);
        return response.data;
      } catch (error) {
        throw new Error(`Failed to get device ${id}: ${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 it's a read operation ('Get'), but doesn't mention authentication requirements, rate limits, error conditions, or what the return format looks like. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 that communicates the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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 read operation with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what information about the device is returned, how to interpret the response, or any behavioral constraints. The context signals show this is a simple tool, but the description doesn't adequately compensate for the lack of structured metadata.

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?

Schema description coverage is 100%, so the schema already documents the single 'id' parameter as a number representing 'Device ID'. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for adequate but unenhanced parameter documentation.

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') and resource ('specific device by ID from Fibaro HC3'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'fibaro_get_devices' which presumably retrieves multiple devices, though the 'by ID' specification provides some implicit 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?

No explicit guidance is provided about when to use this tool versus alternatives. While 'by ID' suggests it's for retrieving a single known device, there's no mention of when to choose this over 'fibaro_get_devices' or other retrieval tools, nor any prerequisites or constraints for usage.

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