Skip to main content
Glama
Sign In
webmin-mcp-server

webmin-mcp-server

by gjenkins20
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_fail2ban_status

Retrieve Fail2ban status for a specific jail or overall, showing currently banned IPs and ban counts.

Instructions

Get Fail2ban status for a specific jail or overall. Returns currently banned IPs and ban counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fail2ban_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jailNoJail name for specific status (optional)
serverNoServer alias (e.g., 'pi1', 'web-server'). Uses default server if not specified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the output (banned IPs and ban counts) but is minimal. No mention of side effects, authentication, or rate limits, which is acceptable for a read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: first states purpose, second states output. No redundant information. Front-loaded 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?

The description does not differentiate from sibling tools list_banned_ips and list_fail2ban_jails, which may confuse an agent. The output description is vague; without an output schema, more detail on the response structure would be helpful.

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 coverage is 100% with descriptions for both parameters. The tool description does not add further parameter details, but the schema already provides meaning. Baseline 3 is appropriate.

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 verb 'Get', the resource 'Fail2ban status', and the scope 'for a specific jail or overall'. It distinguishes from sibling tools like list_banned_ips and list_fail2ban_jails by focusing on status including ban counts and IPs.

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 vs alternatives (e.g., list_banned_ips, list_fail2ban_jails). The description implicitly suggests it's for status, but lacks explicit context for choosing.

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