Skip to main content
Glama

manage_network

Destructive

Create, update, or delete VLAN networks for traffic segmentation. View existing configurations with list_networks before modifying.

Instructions

Create, update, or delete a network. CREATE: provide name, vlanId (>=2 for non-default), enabled, management type. UPDATE: provide networkId + fields to change. DELETE: provide networkId — WARNING: disconnects all clients on that network. Use list_networks to see existing configs before modifying. For VLAN segmentation (e.g. IoT isolation), create a new network with a unique VLAN ID, then assign a WiFi SSID to it with manage_wifi.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesOperation to perform
networkIdNoNetwork ID (required for update/delete, from list_networks)
nameNoNetwork name. Convention: lowercase-with-dashes, e.g. 'trusted', 'iot-devices', 'guest'
enabledNoWhether the network is active
managementNoNetwork management type. Use 'GATEWAY' for standard networks
vlanIdNoVLAN ID: 1 = default network, 2-4009 = custom. Common: 10=trusted, 20=work, 30=iot, 40=guest
Behavior5/5

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

Annotations declare destructiveHint=true, and the description adds a clear warning about client disconnection on delete. Discloses behavioral traits beyond annotations.

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?

Four sentences, front-loaded with main purpose, structured by action. No wasted words.

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

Completeness5/5

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

Covers all three actions, necessary parameters, warnings, and cross-references sibling tools. Adequate for a 6-param, no-output-schema tool.

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?

Input schema has 100% description coverage. Description adds value with naming convention (lowercase-with-dashes), common VLAN IDs, and management type clarification.

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 states the tool creates, updates, or deletes networks, and distinguishes from siblings like list_networks (read) and manage_wifi (WiFi assignment). Verb+resource is specific for each action.

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

Usage Guidelines5/5

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

Explicit guidance for when to use each action, prerequisites (use list_networks before modifying), and a concrete use case for VLAN segmentation. Also warns about disconnecting clients on delete.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pproenca/unifi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server