Skip to main content
Glama
FortiManager MCP Server

FortiManager MCP Server

by rstierli

assign_vap_to_wtp_profile

Adds a VAP (SSID) to selected radios in a FortiAP profile and switches those radios to manual VAP mode so the SSID is broadcast.

Instructions

Add a VAP (SSID) to a FortiAP profile's radios so it gets broadcast.

Reads the profile, appends the VAP to each selected radio's manual VAP list, and switches that radio's vap-all mode to "manual" (the mode that honors an explicit list). VAPs already present are left in place.

Args: device: Managed device name profile: FortiAP (WTP) profile name vap: VAP object name to broadcast radios: Radios to add the SSID to, from 1-3 (default [1, 2]) vdom: VDOM the profile lives in (default "root")

Returns: Update result listing the radios changed

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": {
      "device": "<device>",
      "profile": "<profile>",
      "vap": "<vap>"
    },
    "name": "assign_vap_to_wtp_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
vapYes
vdomNoroot
deviceYes
radiosNo
profileYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A4.1/5.0
Behavior4/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 well: it discloses that the profile is read, the VAP is appended, vap-all is switched to manual, and existing VAPs are preserved. It does not mention permissions, rate limits, or whether a commit/install is required afterward.

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 front-loaded with the core effect, then structured into Args and Returns. Every sentence adds useful information about behavior or parameters, with no wasted text.

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?

The definition is strong for a mutation tool with no annotations: it explains the side effects, idempotent handling of existing VAPs, parameters, and return result. It is only missing workflow context such as whether changes must be committed/installed or what permissions are required.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does: every parameter is explained, including device, profile, VAP name, radios with the 1-3 range and default, and VDOM with its default. The only minor tension is that the schema shows radios default null while the description says default [1, 2].

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 and resource: add a VAP/SSID to a FortiAP profile's radios so it is broadcast. It is clearly distinguishable from nearby CRUD tools, though it does not explicitly name alternatives such as update_device_wtp_profile_radio.

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 description explains the effect of using the tool (appending the VAP and switching vap-all to manual), which implies when it is appropriate. However, it does not state when to use this versus alternatives like update_device_wtp_profile_radio or create_device_vap, nor does it give any exclusions.

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