Skip to main content
Glama
Sign In
FortiManager MCP Server

FortiManager MCP Server

by rstierli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_cli_templates

List CLI templates in a FortiManager ADOM, including names, types, descriptions, and variables, with a limit so you can review available templates and request more if results are cut.

Instructions

List CLI templates in an ADOM, without their scripts.

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

Returns: dict: adom, count, total, cli_templates (name, type, description, variables). 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_cli_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
adomNo
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.13.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavior burden itself. It does disclose the truncation semantics (count vs total, raising limit to page through), which is genuinely useful, but says nothing about required permissions, whether the list is scoped or ordered, or what an empty result means.

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 sentence comes first and the Args/Returns breakdown is easy to scan. The returns paragraph is slightly padded, but every element is doing work; nothing is redundant with the name or title.

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?

An output schema exists, so the description does not need to enumerate return fields, and the extra explanation of count vs total genuinely clarifies the most confusing part of the response. What is missing is context an agent needs to act: no note on permissions, ordering, or how this differs from the sibling list and get tools.

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?

Schema description coverage is 0%, so the description has to compensate, and it does: it explains that adom defaults through the DEFAULT_ADOM env var and falls back to 'root', and that limit defaults to 100 with a minimum of 1. The minimum bound in particular is not present in the schema and would otherwise be invisible to the agent.

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 CLI templates') and adds a useful scope qualifier ('in an ADOM, without their scripts') that tells the agent the payload is a summary listing rather than full template bodies. It stops short of distinguishing itself from siblings like list_templates or get_cli_template, so the reader still has to infer the boundary.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The 'without their scripts' phrase hints at a relationship with get_cli_template but never says to call that tool when the script body is needed.

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