Matter Web Controller

Overview Schema Source Related Servers Discussions Admin

batch_control

Batch update smart-home devices in one request. Provide device IDs and desired brightness or temperature to control multiple devices simultaneously.

Instructions

Control multiple devices at once. Each action: {"id": "...", "brightness": 0.5, "temperature": 4000}.

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": {
      "actions": "<actions>"
    },
    "name": "batch_control"
  }
}

Input Schema

Name	Required	Description	Default
`actions`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.29.0Aug 5, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, and the description only gives an example payload. It does not disclose effects on devices, failure modes, authorization requirements, or whether actions are applied atomically, leaving the agent without critical behavioral expectations.

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 sentence with an inline example, front-loading the core purpose and format. There is no wasted wording.

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?

Given no annotations and a minimal schema, this short description is insufficient for a batch mutation tool. It omits details like error handling, partial success behavior, validation rules, and the full set of supported action properties, despite an output schema existing.

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?

With zero schema description coverage, the description provides the only semantics: actions contain id, brightness, and temperature. However, it does not clarify which fields are required, value ranges, or whether additional properties are accepted, leaving notable gaps.

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 identifies the tool as controlling multiple devices simultaneously, with an example action format. This distinguishes it from single-device siblings like set_device, toggle, and set_level.

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?

The phrase 'Control multiple devices at once' clearly implies a batch usage context and distinguishes this from single-device tools. However, it does not explicitly mention alternatives or exclusions, so it stops short of full guidance.

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