Skip to main content
Glama
amittell

firewalla-mcp-server

by amittell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_flow_trends

Read-only

Retrieve daily blocked flow counts over a specified period (default 30 days), optionally scoped to a box or group, to analyze firewall activity.

Instructions

Blocked flows per day for the last 30 days, one point per day, the last being today so far; period (default 30d) returns the days that overlap it. Without a box it is one GET /v2/trends/flows covering every box, or the box group. That endpoint takes no box, so with box (else FIREWALLA_BOX_ID, unless group is given) each day is counted with one GET /v2/flows status:blocked groupBy=box scoped to the box: 1 request plus 1 per day, ~31 for 30d, of the 100 requests the API allows per 5 minutes. box and group cannot be combined.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boxNoOnly blocked flows of this box (box gid), counted per day: 1 request plus 1 per day (~31 for 30d). Defaults to FIREWALLA_BOX_ID unless group is given; without either, every box. Not with group
groupNoGet trends for a specific box group. Takes precedence over FIREWALLA_BOX_ID; not with box
periodNoReturn the days that overlap this period (default: 30d). The API has no finer resolution than a day, so 1h returns today so far and 24h returns yesterday and today30d
response_formatNoResponse format. 'json' (default): the compact JSON response. 'markdown': the same response as readable markdown, its fields as bullet lists and each list of records as a table of up to 8 columns and DEFAULT_PAGE_SIZE rows (default 100), ending with a line that says what the view leaves out. Omitted or null: 'json'. Errors are JSON either way.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.1

TDQS

A3.9/5.0
Behavior5/5

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

The description adds substantial operational context beyond the annotations: request counts (about 31 for 30d), the 100 requests per 5 minutes rate limit, endpoint-specific behavior, day-level granularity, and the box/group incompatibility. Annotations only provide readOnlyHint and openWorldHint, so this is valuable added disclosure.

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, and nearly every clause contributes useful detail about behavior and request cost. The single dense paragraph with semicolon-separated clauses is information-rich but somewhat harder to parse than a more structured layout.

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 read-only trends tool with no output schema, the description covers aggregation granularity, period semantics, and request cost well. It does not specify the exact fields returned per daily point, but the essential behavior and invocation constraints are complete enough for correct use.

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%, and the parameter descriptions in the schema already explain box, group, period, and response_format in detail. The top-level description largely restates these semantics rather than adding new parameter-level meaning, so the baseline of 3 is appropriate.

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 states a specific resource and aggregation: blocked flows per day for the last 30 days, one point per day. It clearly distinguishes this aggregated trend view from raw flow search, though it does not name a sibling alternative explicitly.

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 explains how to call the tool with and without box/group, and the precedence of group over FIREWALLA_BOX_ID. However, it does not explicitly state when to use this tool versus alternatives like search_flows or get_flow_insights, leaving that comparison to inference.

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