FortiOS 7.6.x MCP Server

wifi_vap_get

Retrieve the configuration of a specific VAP (SSID) by name to view or verify wireless settings.

Instructions

Get a specific VAP (SSID) 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": "wifi_vap_get"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	VAP (SSID) 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.5/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 'gets' configuration, with no mention of whether it is read-only, idempotent, or what happens if the VAP does not exist. This is insufficient for a tool with no annotations.

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, concise sentence that front-loads the key action and resource. Every word serves a purpose with no superfluous content.

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 tool's simplicity (2 parameters, one required, with output schema present), the description is minimally adequate. However, it does not provide any context about expected behavior, error conditions, or relationships to other VAP tools like wifi_vap_create or wifi_vap_delete. The output schema exists but is not referenced in the description.

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 description coverage is 100%, so the input schema already documents both parameters. The description adds no additional meaning or context beyond what is in the schema, so the baseline score 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 'Get a specific VAP (SSID) configuration', using a specific verb and resource. It distinguishes the tool from siblings like wifi_vap_create, wifi_vap_delete, and wifi_vap_list, which perform other operations. The purpose is unambiguous.

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 implies usage when needing details of a single VAP, but does not explicitly state when to use this tool over alternatives like wifi_vap_list, or provide any context on prerequisites or limitations. No exclusions or guidance are given.

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

Deploy Server