Skip to main content
Glama
Sign In
HueMCP

HueMCP

by mbruton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_lights

Lists all lights on the Hue bridge with on/off state, brightness, color, and owner device ID to identify parent devices and map to rooms.

Instructions

List every light on the bridge with on/off state, brightness, colour, and owner.

owner.rid points to the parent device — useful when one device exposes multiple light services. To find which room a light belongs to, cross-reference the device id against list_rooms() children.

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_lights"
  }
}

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
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses output fields and their interpretation (owner.rid points to parent device). Clearly a read-only list operation without side effects, appropriately described.

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 concise sentences with no redundancy. First sentence defines core action, subsequent sentences add valuable context without fluff.

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?

For a zero-parameter list tool with output schema, description explains key fields and cross-referencing hints thoroughly. No missing information needed for agent to understand usage.

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 defined in input schema, so description bears no responsibility for parameter semantics. Schema coverage is 100%, meeting baseline for 0-parameter tools.

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?

Clearly states 'List every light on the bridge' with specific attributes (on/off state, brightness, colour, owner). Distinguishes from sibling list tools by providing unique output details and cross-referencing with 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 Guidelines3/5

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

Provides post-retrieval guidance (owner.rid, cross-reference with list_rooms) but does not explicitly state when to use this tool over siblings or when not to use it. Implied usage through resource specificity.

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