Skip to main content
Glama
FortiManager MCP Server

FortiManager MCP Server

by rstierli

get_local_in_policy6

Retrieves detailed configuration for a specific IPv6 local-in policy in FortiManager by ADOM, policy package, and policy ID, helping users inspect firewall settings.

Instructions

Get detailed information about a specific IPv6 local-in policy.

Args: adom: ADOM name package: Policy package name policyid: Local-in policy6 ID number

Returns: dict: Policy details with keys: - status: "success" or "error" - policy: Full local-in policy6 configuration - message: Error message if failed

Example: >>> result = await get_local_in_policy6("root", "default", 1)

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": {
      "adom": "<adom>",
      "package": "<package>",
      "policyid": "<policyid>"
    },
    "name": "get_local_in_policy6"
  }
}

Input Schema

NameRequiredDescriptionDefault
adomYes
packageYes
policyidYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the tool returns a dict with status, policy, and message fields, including error handling, but does not mention permissions, side effects, or read-only behavior explicitly beyond the implied "get" semantics.

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 purpose is front-loaded in the first sentence, followed by Args, Returns, and Example sections. The example earns its place by showing exact invocation syntax, though the Returns section partially duplicates the existing output schema.

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?

For a simple retrieval tool, the description covers all required arguments, the return structure, and an invocation example. Given the output schema exists and annotations are absent, this is nearly complete, with the main gap being the lack of usage guidance relative to sibling 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?

Schema description coverage is 0%, so the description must compensate. It defines all three required parameters: adom as ADOM name, package as policy package name, and policyid as the local-in policy6 ID number, which adds meaning beyond bare schema titles but remains terse.

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 uses a specific verb and resource: "Get detailed information about a specific IPv6 local-in policy." It distinguishes itself from list_local_in_policies6 and the IPv4 get_local_in_policy by explicitly naming the IPv6 local-in policy, though it does not name those siblings directly.

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 only argument definitions and a call example. It gives no guidance on when to use this tool versus get_local_in_policy, list_local_in_policies6, or other policy-related siblings.

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