Matter Web Controller

Overview Schema Source Related Servers Discussions Admin

add_bridge

Register a remote logical bridge by IP and port. Optionally include an API key to authenticate peers for secure Matter device control.

Instructions

Register a remote logical bridge by IP and port. Optional api_key for authenticated peers (sent in the request body, never the URL).

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": {
      "ip": "<ip>",
      "port": "<port>"
    },
    "name": "add_bridge"
  }
}

Input Schema

Name	Required	Description	Default
`ip`	Yes
`port`	Yes
`api_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.29.0Aug 5, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose a security-relevant behavior: api_key is sent in the request body, never the URL. However, it does not mention other behavioral traits such as idempotency, response format, or prerequisites for successful registration.

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 two sentences, front-loaded with the primary action, and the second sentence adds a necessary nuance about api_key. No unnecessary words or repetition.

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

Completeness4/5

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

For a simple 3-parameter tool with no output schema and no annotations, the description covers the purpose and the meaning of all parameters, including an important security consideration. It omits return values and error scenarios, but these are not critical for this tool's simplicity.

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?

Schema description coverage is 0%, so the description compensates by attaching meaning to each parameter: ip and port are the bridge's address, and api_key is an optional credential for authenticated peers. This goes beyond the raw type definitions in 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 uses the specific verb 'Register' and clearly names the resource ('remote logical bridge') and key connection details (IP and port). This distinguishes it from sibling tools like remove_bridge and register_device.

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 intended use is implied by the purpose ('Register a remote logical bridge'), but the description does not explicitly state when to use this tool versus alternatives like remove_bridge, nor does it provide exclusions or alternative recommendations.

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