Skip to main content
Glama
Sign In
mia

mia

by akadorkin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

host_firewall

Inspect a host's firewall configuration across UFW, fail2ban, ipset, and iptables to audit rules, banned IPs, and MGMT-PORTS chain access.

Instructions

Firewall detail of a host: ufw status numbered, fail2ban jails with the banned IP lists, ipset blacklists (ufw-blacklist.sh) with entry counts, and the MGMT-PORTS iptables chain.

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": {
      "host": "<host>"
    },
    "name": "host_firewall"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYeshost name from the inventory (fleet_hosts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does reveal the concrete data sources and commands behind the result (ufw status numbered, fail2ban, ipset, iptables), which is genuine behavioral context beyond the schema. However, it never states that this is read-only, that it likely requires elevated privileges to query iptables/fail2ban, or how large/slow the collection is.

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?

A single front-loaded sentence that leads with the resource ('Firewall detail of a host') before the itemized contents. The command names (ufw status numbered, ufw-blacklist.sh, MGMT-PORTS) are dense but each earns its place by specifying exactly what is returned.

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 one-parameter read tool with no output schema and no annotations, the description compensates well by enumerating the returned data categories, so an agent knows roughly what comes back. The remaining gap is safety/permission context, which is minor for a diagnostic read but not fully covered.

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?

Only one parameter exists and its schema coverage is 100%, with the schema itself explaining 'host name from the inventory (fleet_hosts)'. Per calibration, high schema coverage sets the baseline at 3 even when the description adds no additional parameter meaning, and this description adds none.

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 names a specific resource ('Firewall detail of a host') and enumerates exactly what is collected: ufw status numbered, fail2ban jails with banned IPs, ipset blacklists, and the MGMT-PORTS iptables chain. An agent can tell this is a firewall-state inspection tool apart from host_inspect or host_ports. It lacks an explicit action verb (get/retrieve), but the resource and scope are unambiguous.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as ufw_rule, fail2ban_unban, or blacklist_update, all of which live in the same sibling namespace and could be confused with a read of firewall state. The diagnostic intent must be inferred from the content listing alone.

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