Skip to main content
Glama
Sign In
UniFi MCP Server

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

attach_carrier_subscriber_host

Attach a gateway host to a UniFi Carrier Fabric subscriber to provision its network access. Specify the subscriber ID and host ID to link the host.

Instructions

Attach a gateway host to a UniFi Carrier Fabric subscriber.

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": {
      "subscriber_id": "<subscriber_id>",
      "host_id": "<host_id>"
    },
    "name": "attach_carrier_subscriber_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to apply the change (required unless dry_run)
dry_runNoPreview the change without applying it
host_idYesGateway host identifier (required)
controllerNoController to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default.
subscriber_idYesSubscriber identifier

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.4
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to apply the change (required unless dry_run)"
    • addedInput schema / properties / dry_run / description
      Added value: +"Preview the change without applying it"
    • addedInput schema / properties / host_id / description
      Added value: +"Gateway host identifier (required)"
    • addedInput schema / properties / subscriber_id / description
      Added value: +"Subscriber identifier"
  2. Addedv0.6.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says 'Attach', implying mutation, but does not disclose the required confirm=true safety gate, dry_run preview semantics, reversibility, permissions, or effects on existing host/subscriber state. For a mutation tool with zero annotation coverage, this 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is efficient but under-specified; conciseness is good, though the brevity leaves behavioral details unaddressed.

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?

The tool is a mutation requiring explicit confirmation, has no annotations, and an output schema exists so return values need not be explained. However, the description omits the confirm/dry_run workflow, controller selection behavior, and what attaching means operationally — leaving key call-time context missing.

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 the schema already documents all five parameters including confirm, dry_run, controller, host_id, and subscriber_id. The description adds no additional parameter meaning beyond what the schema provides, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Attach) and resource (gateway host to a Carrier Fabric subscriber), which is clear and distinct from the sibling detach_carrier_subscriber_host by name. It does not explicitly reference the sibling or clarify scope beyond the single action.

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?

No guidance on when to use this vs detach or other subscriber tools, no prerequisites, and no mention of the confirm/dry_run workflow required for this mutation. The agent must infer usage entirely from the tool name and schema.

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

Deploy Server

Other Tools