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_router_lookup

Look up the best route for a destination IP address in the routing table. Supports optional source interface for PBR and VDOM scoping.

Instructions

Perform a route lookup — find the best route for a destination IP.

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

Input Schema

NameRequiredDescriptionDefault
destinationYesDestination IP address to look up in the routing table.
interfaceNoOptional source interface for PBR lookup.
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.3/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. It only says 'perform a route lookup' with no details on permissions, side effects, or output behavior. This is minimally informative beyond the tool's name.

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 that is front-loaded and efficient. It earns its place without redundancy, though it could benefit from slightly more detail.

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 existence of an output schema (not shown) and lack of annotations, the description is insufficient. It does not explain what the lookup returns or any contextual details critical for agent selection.

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%, with all parameters described adequately in the schema. The description adds no additional semantic value beyond what the schema already provides, meeting the baseline.

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 it performs a route lookup for a destination IP, specifying the action and resource. It distinguishes from sibling tools like monitor_router_lookup6 (IPv6) and other router-related tools.

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 for IPv4 route lookups but provides no explicit guidance on when to use this tool versus alternatives (e.g., monitor_router_lookup6 for IPv6). It does not state when not to use it.

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