Skip to main content
Glama
Sign In
WAF MCP Server

WAF MCP Server

by KratosUAE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

waf_overview

Get a high-level WAF dashboard showing total events, unique IPs, unique rules, and events in the last hour to assess if attention is needed.

Instructions

High-level WAF dashboard: total events, unique IPs, unique rules, events in last hour. Start here to assess if anything needs attention.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoTime window for log search (e.g. '1h', '24h', '7d'). Default: 24h24h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It accurately describes the output as aggregate metrics and implies it is read-only. Additional detail about data boundaries or refresh could improve transparency, but the description is adequate for the simple read 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?

The description is a single concise sentence that front-loads the key metrics and purpose. Every word adds value with no redundancy.

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

Completeness5/5

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

Given the tool's simplicity (one optional parameter, no output schema), the description fully covers its purpose, input, and output. It tells the agent exactly what metrics are returned and when to use this tool.

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 description coverage is 100%, so baseline is 3. The description does not add anything about the 'since' parameter beyond what the schema already provides (default, format examples).

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 tool provides a high-level WAF dashboard with specific metrics (total events, unique IPs, unique rules, events in last hour). It uses a specific verb ('assess') and distinguishes itself from sibling tools that perform specific actions or show detailed data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly recommends starting here to assess if attention is needed, implying it is the entry point. However, it does not provide explicit exclusions or alternatives, though the context of sibling tools makes the usage clear.

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