Matter Web Controller

by dongnh

Overview Schema Source Related Servers Discussions Admin

Python

Local

remove_name

Remove an alias from a Matter device. Provide the device ID and the alias name to delete the alias.

Instructions

Remove an alias from 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>",
      "name": "<name>"
    },
    "name": "remove_name"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.29.0Aug 5, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations available, the description carries the full burden of behavioral disclosure. It only says 'remove', which implies mutation but does not explain consequences, error handling, permissions, or whether the operation is reversible. This is a significant gap for a destructive operation.

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 with no unnecessary words or repetition. It is appropriately sized for the tool's simplicity.

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

Completeness1/5

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

The tool has no output schema, no annotations, and incomplete parameter descriptions. The description is too sparse to guide an agent reliably; it lacks return value information, error scenarios, and any operational context. The complexity is low, but the description does not compensate for the missing structured information.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters. The description mentions 'device' and 'alias', which hints that 'id' likely refers to a device identifier and 'name' to the alias, but it does not explicitly define either parameter. The description adds minimal value beyond the schema.

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 'Remove an alias from a device' uses a specific verb ('remove') and resource ('alias from a device'), clearly distinguishing it from sibling tools like set_name. It unambiguously states the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no when-to-use context or alternatives. It only states what the tool does, leaving the agent to infer usage conditions. There is no mention of prerequisites or exclusions.

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