Matter Web Controller

Overview Schema Source Related Servers Discussions Admin

set_mired

Set a Matter device's color temperature in mireds by providing its ID and the desired mired value. Adjust lighting warmth for smart home control.

Instructions

Set color temperature in mireds for a device.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "mireds": "<mireds>"
    },
    "name": "set_mired"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`mireds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.29.0Aug 5, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and does not mention permissions, reversibility, side effects, or return values. For a mutation tool, this lack of context is a significant gap.

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 a single, concise sentence that front-loads the action and includes the key resource and target. There is no filler or repetition, making it highly efficient.

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?

The tool is simple with two parameters, but the description lacks context about valid mired values, what types of devices are supported, or any behavioral outcomes. Given the absence of annotations and output schema, the description is minimally acceptable but leaves several gaps.

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?

The schema provides only 'id' and 'mireds' with minimal titles, and the description adds meaning by explaining that 'mireds' refers to color temperature and 'device' implies the id is a device identifier. However, it does not define mireds as a unit or clarify the id format, leaving some ambiguity.

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 verb 'set' and the resource 'color temperature in mireds' for a device. This distinguishes it from sibling set tools like set_level or set_ac, making its purpose unambiguous.

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?

The description implies that this tool is used to set color temperature, but it does not explicitly state when to use it versus alternatives like set_level or toggle. No exclusions or alternative suggestions are provided, leaving the usage guidance implied rather than explicit.

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