Skip to main content
Glama

fibaro_device

List, get, and control Fibaro home automation devices. Filter by room, type, or name to manage devices individually or in bulk, including turn on/off, brightness, color, temperature, and Lua access.

Instructions

Device management: list/get/control devices. IMPORTANT: Avoid 'op=list' without filters - it returns 1MB+ of data. Instead: use 'op=get' with 'name' parameter for specific devices, or filter with room_id/type/interface. Supports: turn_on, turn_off, set_brightness, set_color, set_temperature, action, get_lua.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format: text (default) or json (stringified MCP result)
opYesOperation: list|get|action|turn_on|turn_off|set_brightness|set_color|set_temperature|delete|get_lua
device_idNoDevice ID (required for most ops)
actionNoFibaro action name (for op=action)
argsNoAction arguments (for op=action)
levelNoBrightness % (op=set_brightness)
rNo
gNo
bNo
wNoOptional white channel (0-255)
temperatureNoTarget temperature °C (op=set_temperature)
room_idNoFilter for op=list
section_idNoFilter for op=list
typeNoFilter by Fibaro device type for op=list
base_typeNoFilter by baseType for op=list
nameNoFilter by name (case-insensitive, ignores diacritics) for op=list
interfaceNoFilter by interface/capability for op=list
parent_idNoFilter by parent device ID for op=list
enabledNoFilter by enabled for op=list
visibleNoFilter by visible for op=list
deadNoFilter by dead/unresponsive for op=list
propertiesNoFor op=list: return only selected properties (same as list_devices)
Behavior3/5

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

No annotations are provided, so the description carries full burden. It warns about large data with unfiltered list, but lacks details on authentication, rate limits, side effects of actions (e.g., delete), or response format. Partial disclosure.

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 three sentences, front-loaded with purpose, then critical usage advice, then supported operations. No wasted words.

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?

With 22 parameters and no output schema, the description covers usage advice but lacks details on return values, error handling, or parameter dependencies. Adequate but not complete for a complex tool.

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 high (86%), so the description adds minimal extra meaning. It lists supported operations, but those are already in the op parameter description. The 'args' parameter remains undocumented. Baseline score.

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 'Device management: list/get/control devices' and lists specific operations, making the purpose obvious. However, it does not explicitly differentiate from sibling tools like fibaro_home or fibaro_scene, which is a minor gap.

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 guidance: 'Avoid op=list without filters' and recommends using op=get with filters, specifying alternatives and when to use them. This is exemplary usage advice.

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/ikari-software/fibaro-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server