Skip to main content
Glama
Sign In
UniFi MCP Server

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

resume_carrier_subscriber

Resume a suspended UniFi Carrier Fabric subscriber by subscriber ID, with optional dry-run preview or confirmation to apply the change.

Instructions

Resume a suspended 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>"
    },
    "name": "resume_carrier_subscriber"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to apply the change (required unless dry_run)
dry_runNoPreview the change without applying it
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. Changed3 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 / subscriber_id / description
      Added value: +"Subscriber identifier"
  2. Addedv0.6.1

TDQS

B3.2/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 behavioral burden and does not meet it. It doesn't disclose that this is a state-mutating operation, that the schema requires confirm=true to actually apply the change (or dry_run for preview), whether the resume is reversible, or what authorization is needed.

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 wasted words. It errs on the side of under-specification rather than verbosity, but the sizing itself is 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?

An output schema exists and the input schema is fully documented, which reduces what the description must carry. However, for a mutation tool with zero annotations, the description omits the key safety facts an agent needs (that confirm=true is required to apply, or dry_run for preview) and any notion of reversibility.

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 all four parameters (subscriber_id, confirm, dry_run, controller) are already documented, including the confirm/dry_run interplay and controller resolution order. The description adds no additional parameter meaning, so baseline 3 applies.

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 ('Resume') and resource ('UniFi Carrier Fabric subscriber'), and the word 'suspended' scopes it correctly. It does not explicitly name the counterpart suspend_carrier_subscriber, but the verb alone distinguishes it from the other carrier-subscriber siblings.

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 phrase 'a suspended ... subscriber' implies the precondition that this applies only to currently suspended accounts, but there is no explicit when/when-not guidance, no mention of what happens if the subscriber is already active, and no alternative tools referenced.

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