Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

firewall_status

Read-only

Retrieves UFW firewall status, default policies, and rules for a remote Linux server, helping verify firewall configuration and active protections.

Instructions

Get UFW firewall status, default policies, and rules.

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": {
      "server": "<server>"
    },
    "name": "firewall_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered externally. The description adds the useful detail that default policies and rules are included in the response, but says nothing about privilege requirements (UFW status typically needs sudo) or failure behavior when UFW is absent.

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 with no filler or redundant restatement of the name. It is efficiently sized, though the brevity is partly under-specification rather than tightness.

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?

For a one-parameter read-only inspection tool with annotations and no output schema, the definition is minimally adequate: it tells the agent what data comes back. It falls short on the sole parameter and on operational preconditions (sudo/UFW installed) that determine whether the call succeeds.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, server, with 0% schema description coverage, and the description never mentions it. It does not clarify that the call targets a specific remote server identified by that argument, leaving the only parameter entirely explained by its name alone.

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?

Specific verb plus resource: it names UFW explicitly and enumerates what is retrieved (status, default policies, rules). That distinguishes it from adjacent siblings like check_ports or security_audit, though it never names an alternative to route against.

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 when-to-use or when-not-to-use guidance, and no mention of how it differs from check_ports or full_security_audit. An agent can infer it is an inspection call, but nothing in the text states the condition that should select it.

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