Skip to main content
Glama
danjam

MCP Govee

by danjam

set_color_temperature

Set the Kelvin color temperature of Govee lights from warm to cool, specifying a value between 2000 and 9000.

Instructions

Set the color temperature of a Govee device in Kelvin (2000-9000)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYesThe device model
backendNoAPI backend to use: 'v1' (default), 'v2', or 'lan'. Omit to use the server default.
device_idYesThe device MAC address / ID
temperatureYesColor temperature in Kelvin (2000-9000)
Behavior2/5

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

With no annotations, the description carries full burden but fails to disclose behavioral traits beyond setting temperature. No mention of side effects, prerequisites, or state changes.

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?

Single sentence, 12 words, front-loaded with verb and object. No redundancy, every word earns its place.

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

Completeness2/5

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

Tool is simple but no output schema, no behavioral notes, and no error handling information. Lacks response details and boundary conditions.

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 parameters are fully described there. Description only reiterates the Kelvin range already in schema, adding no new meaning.

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?

Description clearly states the action ('Set'), resource ('color temperature'), and constraint ('in Kelvin (2000-9000)'), distinguishing it from sibling tools like set_color, set_brightness, and set_power.

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?

Description implies use for color temperature but provides no explicit guidance on when to use vs alternatives (e.g., set_color for RGB). No exclusion criteria or context provided.

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/danjam/mcp-govee'

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