Remove an IP address from a fail2ban jail (default: sshd). First call validates the IP and previews the action; second call with confirm=true executes the unban.
Remove an IP address from a fail2ban jail (default: sshd).
Call once with confirm=false (or omitted) to validate the IP and see what would happen; nothing runs until you call again with confirm=true.
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes | ||
| jail | No | sshd | |
| confirm | No |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description reveals the critical behavioral trait that nothing runs until confirm=true, which is not visible in annotations or schema. It also clarifies that the first call is a dry-run validation, adding genuine transparency beyond the structured metadata.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no filler. The purpose is front-loaded, and the second sentence explains the confirmation flow without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the operation, the default jail, and the required confirmation flow. Despite no output schema, an agent has enough information to call the tool correctly in its two-phase pattern.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description compensates by explaining the confirm parameter's semantics and noting the default jail. The ip parameter remains self-explanatory, though format or validation details are not provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'Remove an IP address from a fail2ban jail.' It clearly identifies the operation and distinguishes it from siblings like vps_status and vps_list_banned_ips.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear procedural context by explaining the two-step confirm workflow: call with confirm=false to validate, then confirm=true to execute. It does not explicitly mention alternatives or exclusions, but the usage context is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.