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

wifi_wtp_get

Retrieve configuration details for a specific WTP (Access Point) by its serial number or name, optionally targeting a specific VDOM.

Instructions

Get configuration for a specific WTP (Access Point).

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

Input Schema

NameRequiredDescriptionDefault
wtp_idYesWTP (AP) serial number or name.
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.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but it only states the basic purpose. It does not disclose behavioral traits like whether it is read-only, error behavior (e.g., if WTP not found), or permissions required. The name implies read-only, but this is not explicit.

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, front-loaded sentence with no wasted words. It is efficient, though slightly under-specified; adding a bit more context would improve it without sacrificing conciseness.

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, output schema exists), the description is minimally adequate. It covers the core function but omits context such as when to use Get vs List, or what the output contains. No annotations further limit completeness.

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%, with each parameter already well-described (wtp_id as serial/name, vdom with default and wildcard note). The tool description adds no additional meaning beyond the schema, so baseline 3 applies.

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 states 'Get configuration for a specific WTP (Access Point),' clearly indicating the verb ('Get'), resource ('configuration for a specific WTP'), and scope. This distinguishes it from sibling tools like wifi_wtp_list (list) and wifi_wtp_deauthorize (deauthorize).

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?

The description provides no guidance on when to use this tool versus alternatives such as wifi_wtp_list or wifi_wtp_profile_get. No prerequisites, scenarios, or exclusions 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

Other Tools