Skip to main content
Glama
paoloamato2

FortiOS 7.6.x MCP Server

by paoloamato2

log_query

Query logs from FortiOS with flexible filtering. Returns entries including timestamps, sources, destinations, actions, and UTM verdicts.

Instructions

Query logs from FortiOS with flexible filtering.

Returns log entries from the specified backend and type. Results include timestamps, sources, destinations, actions, and UTM verdicts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoLog storage backend: disk, memory, fortianalyzer, forticloud. Use 'disk' (default) for local logs.disk
log_typeNoLog type: traffic, event, utm, virus, webfilter, attack, spam, anomaly, voip, dlp, app-ctrl, emailfilter, dns, ssh, ssl, file-filter. For traffic subtypes use: traffic/forward, traffic/local, traffic/sniffer.traffic
filter_exprNoFilter expression. FortiOS filter syntax. Examples: 'srcip==10.0.0.1', 'action==blocked', 'user==john'. Combine with 'and': 'srcip==10.0.0.1 and dstport==443'.
rowsNoMaximum number of log entries to return (1-10000).
startNoOffset for pagination.
extra_paramsNoAdditional query parameters as a dict.
vdomNoTarget VDOM name. Defaults to the server default VDOM. Use '*' for all VDOMs (super-admin required).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations exist, so the description carries the burden. It states the tool returns log entries with fields (timestamps, sources, etc.), confirming it is read-only. However, it does not mention pagination behavior, rate limits, or potential performance impact beyond what the schema (rows, start) implies. No contradictions.

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 two concise sentences with no extraneous information. It front-loads the purpose. Could be more structured but is effective and efficient.

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 output schema exists, return values are covered. The description mentions backend and type but does not explain the flexibility of filter_expr or the vdom parameter. For a tool with many parameters and sibling tools, it lacks completeness about scope and prerequisites, though schema fills some gaps.

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 parameters are already well-documented. The description adds no additional meaning beyond 'flexible filtering'. Baseline 3 is appropriate as the description does not need to repeat schema, but it also does not enhance understanding.

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 clearly states 'Query logs from FortiOS with flexible filtering' and mentions returning entries with common fields, establishing it as a general log query tool. It distinguishes from specialized sibling log tools (e.g., log_traffic_forward, log_virus) by not specifying a log subtype, but could explicitly contrast them.

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?

No guidance is provided on when to use this tool versus the many specific log_* tools (e.g., log_traffic_forward, log_app_ctrl). The description does not mention alternatives or conditions. A statement like 'Use for cross-type queries; for specific types, use the dedicated log_* tools' would help.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paoloamato2/fortinet-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server