Skip to main content
Glama
Sign In
HueMCP

HueMCP

by mbruton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_zones

List all lighting zones with their grouped light IDs and member lights. Use zone IDs with set_group to control devices across multiple rooms.

Instructions

List zones with their grouped_light_id (use with set_group) and member lights.

Zones differ from rooms: a light belongs to exactly one room but can be in many zones (e.g. a "Downstairs" zone spanning Kitchen + Living room).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so description carries the full burden. It describes the output (zones with ids and member lights) and distinguishes from rooms, but does not mention any behavioral traits like idempotency, rate limits, or permissions. However, the tool appears to be a read-only list operation, so the description is adequate but not thorough.

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?

Two concise, well-structured sentences. The first sentence states the primary action and important fields; the second provides a clarifying distinction from rooms. No unnecessary verbiage.

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

Completeness5/5

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

Given no parameters and presence of an output schema, the description is complete. It explains what the tool returns (grouped_light_id and member lights), its relationship to set_group, and how zones differ from rooms. No aspect is missing for a simple list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist (input schema is empty). Schema coverage is trivially 100%. The description does not need to add parameter info, and its focus on output and usage is sufficient. Baseline for 0 parameters is 4.

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 tool lists zones with grouped_light_id and member lights, and explicitly distinguishes zones from rooms, which differentiates it from sibling tools like list_rooms.

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?

Provides clear context for when to use (e.g., to get grouped_light_id for set_group, or to view member lights). Includes comparison with rooms to guide tool selection, though no explicit when-not-to-use.

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