Skip to main content
Glama
Sign In
Homey MCP Server

Homey MCP Server

by homey-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Devices

list_devices
Read-onlyIdempotent

List Homey devices with live capability values, including ID, name, class, zone, availability, and sensor states. Filter by room name or device class to find specific devices.

Instructions

List all Homey devices with current capability values. Returns device ID, name, class, zone, availability, capabilities, and live sensor/state values. Use 'zone' to filter by room name (partial match) or 'class' to filter by device type (light, sensor, thermostat, speaker, lock, socket, etc).

Input Schema

NameRequiredDescriptionDefault
zoneNoFilter by zone name (partial match, e.g. 'kitchen')
classNoFilter by device class (e.g. light, sensor, thermostat, speaker, lock, socket)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by enumerating the returned fields (ID, name, class, zone, availability, capabilities, live values) and clarifying that filtering is partial-match rather than exact.

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?

Three tight sentences: purpose first, return shape second, filtering third. No filler, no repetition, and the most useful information is front-loaded.

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?

With no output schema, the description carries the burden of describing the return payload and does so adequately with a field enumeration. Minor gaps remain around volume (how many devices can be returned) and behavior when a filter matches nothing.

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 both parameters are already documented with identical examples. The description restates the same partial-match and class-example semantics rather than adding new meaning such as case sensitivity or fallback behavior when no match occurs.

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?

States a specific verb and resource ('List all Homey devices') plus what data comes back (capability values). It does not name the closest sibling, search_devices, so the boundary between a full listing and a search is left for the agent to infer.

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

Usage Guidelines3/5

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

Explains how to use both filter parameters with concrete examples, which implies the read-all-then-filter workflow. However, there is no guidance on when to prefer search_devices or get_device instead, and no stated exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools