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

monitor_vpn_ipsec_tunnel_up

Activate an IPsec VPN tunnel by specifying its name. Optionally target a specific VDOM.

Instructions

Bring up (activate) an IPsec VPN tunnel.

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": {
      "tunnel_name": "<tunnel_name>"
    },
    "name": "monitor_vpn_ipsec_tunnel_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
tunnel_nameYesIPsec tunnel (Phase 1) name to bring up.
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

C2.9/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 'bring up (activate)' without mentioning prerequisites, side effects, or state changes. Minimal transparency.

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 description is a single sentence, highly concise and front-loaded. It serves its purpose efficiently, though it could include brief usage context without adding length.

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

Completeness2/5

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

Given the presence of an output schema, the description does not explain return values. It lacks critical information on required permissions, error conditions, or side effects, making it incomplete for safe agent use.

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?

Schema coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions. Parameters are self-explanatory from 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?

The description clearly states the action ('bring up/activate') and the resource ('IPsec VPN tunnel'), distinguishing it from the sibling 'monitor_vpn_ipsec_tunnel_down'. However, it does not explicitly differentiate from other VPN tools like 'monitor_vpn_ipsec'.

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 on when to use this tool versus alternatives, such as the inverse 'monitor_vpn_ipsec_tunnel_down'. The description lacks context for effective tool 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