FortiOS 7.6.x MCP Server

vpn_ipsec_phase1_get

Retrieve IPsec Phase 1 interface configuration by tunnel name. Optionally specify a VDOM to target configurations in multi-VDOM setups.

Instructions

Get a specific IPsec Phase 1 interface configuration.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Phase 1 tunnel name.
`vdom`	No	Target VDOM name. Defaults to the server default VDOM. Use '*' for all VDOMs (super-admin required).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 25, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states it is a 'Get' operation, implying it is read-only, but does not disclose any other behavioral aspects such as required permissions, error handling, rate limits, or what happens if the resource is not found.

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 a single sentence of 8 words, highly concise and front-loaded with the core action. No words are wasted.

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?

Given that an output schema exists (so return values are documented elsewhere) and the tool has low complexity (simple get with two parameters), the description is complete enough for an agent to understand its purpose and usage.

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 input schema has 100% description coverage for its two parameters ('name' and 'vdom'), so the schema already documents their meaning. The description adds no additional meaning beyond the schema, resulting in a baseline score of 3.

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 'Get a specific IPsec Phase 1 interface configuration', using a specific verb ('Get') and resource ('specific IPsec Phase 1 interface configuration'). It distinguishes from sibling tools like 'list', 'create', 'delete', and 'update' which have different actions.

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?

The description implicitly indicates usage when a specific configuration is needed by name, but provides no explicit guidance on when to use this tool versus alternatives like 'vpn_ipsec_phase1_list'. No when-not conditions or alternative tool names are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server