Skip to main content
Glama
kaeljune

Fibaro HC3 MCP Server

by kaeljune

fibaro_set_device_value

Set advanced device properties like temperature setpoints, modes, or custom parameters in Fibaro Home Center 3 smart home systems. Use for specialized property adjustments beyond basic brightness or color controls.

Instructions

Set a specific property value for a device. Use this ONLY for advanced properties like temperature setpoints, modes, or custom device properties. Do NOT use for brightness (use fibaro_set_brightness) or colors (use fibaro_set_color).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDevice ID
propertyYesProperty name to set (e.g., "targetTemperature", "mode", "state")
valueYesValue to set

Implementation Reference

  • MCP tool handler for 'fibaro_set_device_value': extracts id, property, value from args, calls fibaroClient.setDeviceValue, and returns success message.
    case 'fibaro_set_device_value': {
      if (!this.fibaroClient) {
        throw new Error('Not connected to Fibaro HC3. Please check your configuration and restart the MCP server.');
      }
      const deviceId = args?.id as number;
      const property = args?.property as string;
      const value = args?.value;
      await this.fibaroClient.setDeviceValue(deviceId, property, value);
      return {
        content: [
          {
            type: 'text',
            text: `Successfully set device ${deviceId} property '${property}' to '${value}'`,
          },
        ],
      };
    }
  • src/index.ts:192-213 (registration)
    Registration of the 'fibaro_set_device_value' tool in the MCP tools list, including input schema.
    {
      name: 'fibaro_set_device_value',
      description: 'Set a specific property value for a device. Use this ONLY for advanced properties like temperature setpoints, modes, or custom device properties. Do NOT use for brightness (use fibaro_set_brightness) or colors (use fibaro_set_color).',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Device ID',
          },
          property: {
            type: 'string',
            description: 'Property name to set (e.g., "targetTemperature", "mode", "state")',
          },
          value: {
            type: ['string', 'number', 'boolean'],
            description: 'Value to set',
          },
        },
        required: ['id', 'property', 'value'],
      },
    },
  • Input schema definition for the fibaro_set_device_value tool.
    {
      name: 'fibaro_set_device_value',
      description: 'Set a specific property value for a device. Use this ONLY for advanced properties like temperature setpoints, modes, or custom device properties. Do NOT use for brightness (use fibaro_set_brightness) or colors (use fibaro_set_color).',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Device ID',
          },
          property: {
            type: 'string',
            description: 'Property name to set (e.g., "targetTemperature", "mode", "state")',
          },
          value: {
            type: ['string', 'number', 'boolean'],
            description: 'Value to set',
          },
        },
        required: ['id', 'property', 'value'],
      },
    },
  • FibaroClient helper method that performs the actual API POST to /api/devices/{id}/action/setProperty with args [property, value]. Called by the MCP handler.
    async setDeviceValue(id: number, property: string, value: any): Promise<void> {
      try {
        await this.client.post(`/api/devices/${id}/action/setProperty`, {
          args: [property, value]
        });
      } catch (error) {
        throw new Error(`Failed to set device ${id} property ${property} to ${value}: ${error}`);
      }
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a mutation operation ('Set') but doesn't disclose behavioral traits like required permissions, error handling, or response format. The description adds some context about property types but lacks details on side effects or system 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 is front-loaded with the purpose and usage guidelines in two concise sentences, with zero wasted words. Every sentence earns its place by providing critical differentiation from sibling tools.

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

Completeness4/5

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

Given the complexity (mutation tool with no annotations and no output schema), the description is reasonably complete for its purpose. It clearly defines the tool's scope and exclusions, though it could benefit from more behavioral details like error conditions or response expectations to be fully comprehensive.

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 all three parameters (id, property, value). The description adds minimal semantic context by mentioning examples like 'temperature setpoints, modes', which loosely relates to the 'property' parameter but doesn't provide additional syntax or format details beyond the schema.

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

Purpose5/5

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

The description clearly states the specific action ('Set a specific property value') and resource ('for a device'), distinguishing it from siblings like fibaro_set_brightness and fibaro_set_color by specifying it's for advanced properties like temperature setpoints, modes, or custom device properties.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidelines: 'Use this ONLY for advanced properties like temperature setpoints, modes, or custom device properties' and 'Do NOT use for brightness (use fibaro_set_brightness) or colors (use fibaro_set_color)', clearly indicating when to use this tool versus alternatives.

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