Skip to main content
Glama
Sign In
crowdsec-ops-mcp

crowdsec-ops-mcp

by frli4797
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

top_offenders

Identify top attacking IP addresses by analyzing recent CrowdSec alert volume over a configurable time window.

Instructions

Return top source IPs by recent CrowdSec alert volume.

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": "top_offenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNoLookback window such as 15m, 6h, 24h, 7d.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/5.0
Behavior2/5

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

Without annotations, the description fails to disclose behavioral aspects like default window, maximum number of IPs returned, or any side effects. It only says 'recent' without specifying a default lookback or how results are ordered.

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?

The description is a single, concise sentence that immediately conveys the tool's purpose. No extraneous words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and annotations, the description is too brief. It does not specify return format, default windows, or what 'top' means (count or limit), leaving agents with incomplete information.

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 a clear parameter description. The tool description adds no additional semantic value beyond what the schema already provides for the 'window' parameter, so baseline score of 3 applies.

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 'Return' and the resource 'top source IPs by recent CrowdSec alert volume', making the tool's purpose unambiguous. It distinguishes itself from sibling tools like 'recent_crowdsec_alerts' and 'inspect_ip' by focusing on aggregated top offenders.

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 versus alternatives such as 'inspect_ip' or 'recent_crowdsec_alerts'. There are no usage scenarios, prerequisites, or exclusions mentioned.

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