Skip to main content
Glama

List Firewalla Devices

firewalla_list_devices
Read-onlyIdempotent

List all devices tracked by Firewalla to identify unknown devices, monitor network activity, and audit security configurations for potential risks.

Instructions

Inventory every device Firewalla tracks — the "who's on my network right now" primitive.

Use this to answer:

  • "Are there any unknown/rogue devices on my network?"

  • "Which devices aren't being monitored?"

  • "What's the MAC vendor breakdown across my network?"

  • "Any router-class devices I didn't expect?"

Args:

  • box (string, optional): Filter to devices on a specific box gid.

  • online_only (boolean, optional): Drop offline devices client-side.

  • response_format ('markdown' | 'json'): Output format (default: markdown).

Returns: { count: number, // devices after client-side filtering total: number, // devices returned by the API (pre-filter) devices: Array<{ id: string, // typically MAC gid: string, // box the device is attached to name: string, ip: string, mac?: string, macVendor?: string, ipReserved?: boolean, online: boolean, network?: { id, name }, deviceType?: string, // e.g. "phone", "computer", "iot" isRouter?: boolean, isFirewalla?: boolean, monitoring?: boolean, // false = device excluded from monitoring totalDownload?: number, // bytes (lifetime) totalUpload?: number }> }

Audit framing:

  • Unknown macVendor → possible squatter or spoofed MAC.

  • monitoring=false → device is excluded from Firewalla's visibility; review whether that's intentional.

  • Unexpected isRouter=true → shadow router on the LAN.

  • ipReserved=false on a server that should have a static lease → risk of address drift.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boxNoFilter to devices attached to a specific box gid.
online_onlyNoIf true, drop offline devices from the response. Client-side filter — the API returns all devices either way.
response_formatNoOutput format. 'markdown' (default) renders human-readable audit tables. 'json' returns structured data suitable for chaining into another tool call.markdown
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds valuable behavioral context about client-side filtering ('online_only' drops offline devices client-side), output format implications, and audit interpretations that help the agent understand how to process and interpret results beyond basic safety information.

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 well-structured with clear sections (purpose, usage questions, args, returns, audit framing) and every sentence adds value. While somewhat lengthy, it's efficiently organized with bullet points and structured returns documentation, making it easy to parse. Minor deduction for being slightly verbose in the returns section.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and the absence of an output schema, the description provides comprehensive context including detailed return structure documentation, audit interpretation guidance, and clear usage scenarios. With annotations covering safety aspects and the description filling in behavioral and interpretive gaps, this provides complete context for the agent to effectively use this tool.

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 the schema already fully documents all three parameters. The description adds minimal additional context beyond what's in the schema (e.g., 'client-side filter' for online_only, output format implications), but doesn't provide significant semantic value beyond the structured documentation. Baseline 3 is appropriate given complete schema coverage.

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 the tool's purpose as 'Inventory every device Firewalla tracks' and positions it as the 'who's on my network right now' primitive. It distinguishes from siblings by focusing on device inventory rather than alarms, rules, flows, or boxes, making the scope specific and differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage scenarios with bullet points answering specific questions like 'Are there any unknown/rogue devices on my network?' and 'Which devices aren't being monitored?'. It also includes an 'Audit framing' section that guides interpretation of results, effectively telling the agent when and how to use this tool for network auditing purposes.

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/productengineered/firewalla-mcp'

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