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

crowdsec-ops-mcp

by frli4797
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

security_summary

Summarize recent CrowdSec decisions and alerts over a configurable lookback window to provide a quick overview of security events.

Instructions

Summarize recent CrowdSec decisions and alerts.

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

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

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the burden but provides no behavioral details. It does not indicate read-only status, side effects, or output format. This is insufficient for safe invocation.

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

Conciseness3/5

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

One sentence is efficient, but it lacks structure and misses key details. It is not overly verbose, but could be more informative without adding length.

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 complexity (1 optional parameter, no output schema, many siblings), the description is incomplete. It does not explain output, differentiation from siblings, or prerequisites.

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% and the parameter description is clear. The tool description adds no extra meaning beyond the schema, but the schema itself is adequate.

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?

The description states the tool summarizes CrowdSec decisions and alerts, distinguishing it from siblings like recent_crowdsec_alerts or recent_crowdsec_decisions. However, 'summarize' is vague and could mean an aggregated view vs a list.

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 over siblings. It does not mention alternatives or scenarios where a summary is preferred over detailed lists.

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