Skip to main content
Glama
Sign In
FortiOS 7.6.x MCP Server

FortiOS 7.6.x MCP Server

by paoloamato2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

vpn_certificate_local_list

List all VPN local (device) certificates on the FortiGate, optionally filtered by VDOM.

Instructions

List all VPN local (device) certificates.

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": "vpn_certificate_local_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
vdomNoTarget VDOM name. Defaults to the server default VDOM. Use '*' for all VDOMs (super-admin required).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states the listing action, ignoring read-only nature, pagination, or authentication needs. The tool could be confused with similar certificate listers.

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 extremely concise (6 words) and front-loaded. Every word is necessary; no fluff. Perfect for a simple list operation.

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

Completeness3/5

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

Given the presence of many similar sibling tools and the existence of an output schema, the description is minimally adequate but lacks explanation of the scope (e.g., what 'local device' means) or differentiation from generic certificate list tools.

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

Parameters3/5

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

The single parameter 'vdom' is fully documented in the input schema (100% coverage), so the description adds no extra meaning. Baseline of 3 is appropriate.

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 action 'List' and the resource 'VPN local (device) certificates', which is specific and distinguishes it from sibling tools like vpn_certificate_ca_list or certificate_local_list.

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?

No guidance is provided on when to use this tool versus alternatives such as vpn_certificate_ca_list or certificate_local_list. The agent receives no context for selection.

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