Skip to main content
Glama
FortiManager MCP Server

FortiManager MCP Server

by rstierli

list_templates

List provisioning templates in an ADOM to review available IPsec, BGP, system, and other template types; adjust the limit to retrieve more results.

Instructions

List all provisioning templates in an ADOM.

Returns all template types: IPsec, BGP, system, etc.

Args: adom: ADOM name (default: from DEFAULT_ADOM env var, or "root") limit: Maximum number of templates to return (default: 100, minimum: 1)

Returns: List of templates with name, type, and settings. count is the number returned and total the number before limit: if total is larger the list was cut, raise limit for the rest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
adomNo
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 meaningful work: it discloses the return shape (name, type, settings) and the truncation contract — count is what was returned, total is the pre-limit count, and a larger total means the list was cut and limit should be raised. It does not mention read-only safety, permissions, or ADOM access requirements, which is the remaining 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?

Front-loaded with the purpose, then a type enumeration, then Args/Returns blocks with zero filler. The docstring-style Args list mildly restates the schema, but every sentence carries information, and the truncation note is placed where an agent will look for it.

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?

For a two-parameter read tool, this covers purpose, both parameters with defaults and bounds, and pagination semantics. An output schema exists, so the additional Returns detail is a bonus rather than a requirement; nothing an agent needs in order to call it correctly is missing.

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 an ADOM name with a DEFAULT_ADOM env-var fallback to "root", and limit is given a default of 100 and a minimum of 1 that the schema does not encode. Both parameters gain meaning beyond the bare types in the schema.

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 ("List all provisioning templates in an ADOM") and clarifies scope by enumerating the template types it covers (IPsec, BGP, system). It does not explicitly name the type-specific siblings (list_cli_templates, list_system_templates, list_sdwan_templates), so the generic-vs-specialized distinction is only implied.

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?

Usage is implied by "all provisioning templates in an ADOM" — the agent can infer this is the unfiltered, all-types listing — but there is no explicit when-to-use versus when to prefer a type-specific sibling, and no stated prerequisites or 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