Skip to main content
Glama

cf_query_firewall_events_raw

Retrieve raw firewall events for a zone over a specified time window, with filters and pagination to investigate security incidents.

Instructions

Raw firewall events (one row per individual event) over a time window.

Calls: POST /graphql, firewallEventsAdaptive dataset.

Args:
    zone_id: zone tag.
    since, until: ISO-8601 time range.
    filters: extra filter terms.
    limit: rows per page, clamped to [1, 500]. Default 50.
    cursor: continuation token.
    verbose: when True, includes additional fields like userAgent,
        referer, rayName, clientRequestPath. Subject to the same
        ~20K-token response ceiling — narrow `limit` accordingly.

Returns: envelope with `data = {rows, count, page}` and `next_cursor`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_idYes
sinceYes
untilYes
filtersNo
limitNo
cursorNo
verboseNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description discloses important behavioral traits: limit clamping, verbose mode impact on response size, pagination via cursor, and the ~20K-token ceiling. It does not cover authentication or side effects but provides sufficient transparency.

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 well-structured with a purpose summary, then sections for calls, arguments, and return. It is concise and front-loads essential information.

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 7 parameters, output schema presence, and no nested objects, the description covers all input semantics, return envelope, and critical constraints like limit clamping and verbose ceiling. It is fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage; the description adds full meaning for all 7 parameters: zone_id, since/until (ISO-8601), filters, limit (clamping+default), cursor, verbose (fields+ceiling). This significantly exceeds schema information.

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 returns raw firewall events, one row per event, over a time window. It distinguishes itself from siblings like grouped queries.

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 indicates usage for raw events over a time window but does not explicitly state when to use this tool versus alternatives like grouped queries. However, the context is clear.

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/wojtekkura/cf-mcp'

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