Skip to main content
Glama
frli4797

crowdsec-ops-mcp

by frli4797

unban_ip

Prepare an audited cscli command to remove a CrowdSec ban for a specified IP address.

Instructions

Prepare and audit a potential cscli command to delete a CrowdSec decision for one IP. The MCP does not execute it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYesIPv4 or IPv6 address to inspect or operate on.
reasonNo
executeNoLegacy no-op flag. The MCP never executes writes; it only prepares an audited potential cscli command.
Behavior4/5

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

Clearly states the MCP does not execute the command, only prepares it. Explains the 'execute' parameter is a legacy no-op. With no annotations, this is good disclosure of non-destructive behavior.

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 that immediately convey purpose and key constraint. Every word earns its place.

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?

Lacks explanation of what 'audit' means, the output format, or prerequisites like CrowdSec installation. Given no output schema and only moderate schema coverage, description could be more complete.

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 67% (ip and execute described; reason missing). Description adds no value for reason and only restates execute's no-op nature. No compensation for the undocumented reason parameter.

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?

States it prepares an audited cscli command to delete a CrowdSec decision for an IP. Clear action and resource, but does not explicitly differentiate from sibling tools like ban_ip or allow_ip.

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 on when to use this tool versus alternatives like ban_ip or allow_ip. Only implies usage when user wants to unban but not execute directly.

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/frli4797/crowdsec-mcp'

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