Skip to main content
Glama
Sign In
FortiManager MCP Server

FortiManager MCP Server

by rstierli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_devices_bulk

Register multiple FortiManager devices in one ADOM simultaneously, reducing manual entry by submitting bulk device configurations as a task.

Instructions

Add multiple devices to FortiManager in bulk.

Registers multiple devices at once for efficiency.

Args: adom: ADOM name where devices will be added devices: List of device configurations. Each device dict can contain: - name: Device display name (required) - ip: Device IP address - sn: Serial number - adm_usr: Admin username - adm_pass: Admin password - desc: Description - platform_str: Platform type - os_ver: OS version flags: Additional flags like ["create_task"]

Returns: dict: Bulk add result with keys: - status: "success" or "error" - requested_count: Number of devices in the request. NOT a count of devices actually added: the add runs as a task, so per-device results only exist once it completes. - task_id: Task ID if run as background task - message: Error message if failed

Example: >>> devices = [ ... {"name": "FGT-Site1", "ip": "192.0.2.1", "adm_usr": "admin", "adm_pass": "pass1"}, ... {"name": "FGT-Site2", "ip": "192.0.2.2", "adm_usr": "admin", "adm_pass": "pass2"}, ... ] >>> result = await add_devices_bulk("root", devices)

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": {
      "adom": "<adom>",
      "devices": "<devices>"
    },
    "name": "add_devices_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
adomYes
flagsNo
devicesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the add runs as an asynchronous task, that requested_count is NOT the number actually added, and that per-device results only exist after the task completes. It also documents the response keys (status, task_id, message) and the create_task flag. It does not mention required permissions or failure modes beyond a generic error message.

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?

The purpose statement is front-loaded before args, returns and example, and every section is scannable. The doctest-style example is somewhat long but earns its place given the nested device dicts; the sentence "Registers multiple devices at once for efficiency" slightly restates the opening line.

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 3-parameter mutation tool with no annotations, the description covers inputs, the async task caveat, and return keys thoroughly. Minor omissions remain: no stated prerequisites (ADOM existence, credentials handling for adm_pass) and no guidance on what to do with task_id after the task is launched.

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 coverage is 0%, so the description must compensate and it does: adom is explained as the target ADOM, devices is expanded into a full field list with required/optional status (name required; ip, sn, adm_usr, adm_pass, desc, platform_str, os_ver optional), and flags is illustrated with ["create_task"]. A worked example reinforces the nested device dict shape.

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?

"Add multiple devices to FortiManager in bulk" names a specific verb (add), resource (devices) and scope (bulk, multiple at once), which implicitly separates it from the singular add_device sibling. It stops short of explicitly naming or contrasting any sibling tool, so it falls just below the top mark.

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?

"Registers multiple devices at once for efficiency" implies the bulk tool is preferred when adding many devices, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative (e.g. add_device for a single device). Usage is implied rather than stated.

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