Skip to main content
Glama
kaeljune

Fibaro HC3 MCP Server

by kaeljune

fibaro_set_brightness

Adjust lighting brightness or dimmer levels for smart home devices by specifying a percentage value from 0 to 100. Use this tool to control light intensity in your Fibaro Home Center 3 system.

Instructions

Set brightness or dimmer level for lights and dimmable devices. Use this when user mentions brightness, dimming, intensity, or percentage levels (0-100%). Keywords: bright, dim, brightness, level, percent, %.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDevice ID
brightnessYesBrightness level (0-100)

Implementation Reference

  • MCP tool handler for fibaro_set_brightness: checks Fibaro connection, extracts device ID and brightness arguments, delegates to FibaroClient.setBrightness method, and returns formatted success response.
    case 'fibaro_set_brightness': {
      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 brightness = args?.brightness as number;
      await this.fibaroClient.setBrightness(deviceId, brightness);
      return {
        content: [
          {
            type: 'text',
            text: `Successfully set brightness for device ${deviceId} to ${brightness}%`,
          },
        ],
      };
    }
  • Input schema defining parameters for fibaro_set_brightness tool: device ID (number) and brightness (number between 0-100), both required.
    inputSchema: {
      type: 'object',
      properties: {
        id: {
          type: 'number',
          description: 'Device ID',
        },
        brightness: {
          type: 'number',
          description: 'Brightness level (0-100)',
          minimum: 0,
          maximum: 100,
        },
      },
      required: ['id', 'brightness'],
    },
  • src/index.ts:214-233 (registration)
    Registration of fibaro_set_brightness tool in the ListTools response, including name, description, and input schema.
    {
      name: 'fibaro_set_brightness',
      description: 'Set brightness or dimmer level for lights and dimmable devices. Use this when user mentions brightness, dimming, intensity, or percentage levels (0-100%). Keywords: bright, dim, brightness, level, percent, %.',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Device ID',
          },
          brightness: {
            type: 'number',
            description: 'Brightness level (0-100)',
            minimum: 0,
            maximum: 100,
          },
        },
        required: ['id', 'brightness'],
      },
    },
  • FibaroClient.setBrightness helper method: performs HTTP POST request to Fibaro HC3 API endpoint /api/devices/{id}/action/setValue with brightness value as argument.
    async setBrightness(id: number, brightness: number): Promise<void> {
      try {
        await this.client.post(`/api/devices/${id}/action/setValue`, {
          args: [brightness]
        });
      } catch (error) {
        throw new Error(`Failed to set brightness for device ${id} to ${brightness}: ${error}`);
      }
    }
Behavior2/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 of behavioral disclosure. It describes the action ('Set brightness or dimmer level') but lacks details on behavioral traits such as required permissions, whether the change is immediate or reversible, error handling, or rate limits. For a mutation tool with zero annotation coverage, this is a significant gap, though it does specify the percentage range (0-100%).

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 appropriately sized and front-loaded: the first sentence states the purpose, and the second provides usage guidelines and keywords. Every sentence earns its place with no wasted words, making it efficient and easy to parse.

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?

Given the tool's complexity (a mutation tool with 2 parameters), no annotations, and no output schema, the description is moderately complete. It covers purpose and usage but lacks behavioral details like error handling or response format. It's adequate for basic use but has clear gaps for an AI agent to fully understand the tool's behavior and outcomes.

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 clear documentation for both parameters ('id' and 'brightness'), including the brightness range (0-100). The description adds minimal value beyond the schema by mentioning 'percentage levels (0-100%)' and keywords, but it doesn't provide additional semantic context (e.g., how 'id' relates to devices). Baseline 3 is appropriate when 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 tool's purpose: 'Set brightness or dimmer level for lights and dimmable devices.' It specifies the verb ('Set') and resource ('brightness or dimmer level for lights and dimmable devices'), making it easy to understand. However, it doesn't explicitly differentiate from siblings like 'fibaro_set_color' or 'fibaro_set_device_value,' which might also handle brightness in some contexts, so it doesn't reach the highest score.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: 'when user mentions brightness, dimming, intensity, or percentage levels (0-100%).' It includes keywords like 'bright, dim, brightness, level, percent, %' to guide usage. However, it doesn't explicitly state when not to use it or name alternatives (e.g., 'fibaro_set_color' for color changes), so it falls short of a perfect score.

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