Skip to main content
Glama

cf_baseline_traffic_diff

Compare traffic from an attack window against a prior baseline on the same path to identify anomalies in edge response status and client country distributions.

Instructions

Compare attack-window traffic vs a prior baseline window on the same path.

Runs two `httpRequestsAdaptiveGroups` queries grouped by
`edgeResponseStatus` and `clientCountryName`, returning a side-by-side
diff suitable for the ATK archetype workflow.

Args:
    zone_id: zone tag.
    match_path: exact `clientRequestPath` to filter (e.g. '/oauth/token').
    attack_since, attack_until: ISO-8601 attack window.
    baseline_lookback_days: how many days before `attack_since` to align
        the baseline window (defaults to 7).

Calls: POST /graphql, two httpRequestsAdaptiveGroups queries.

Returns: envelope with `data = {attack: {...}, baseline: {...},
    window_seconds: N, zone_id, match_path}`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_idYes
match_pathYes
attack_sinceYes
attack_untilYes
baseline_lookback_daysNo

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 carries full burden. It discloses that the tool runs two GraphQL queries, groups by fields, and returns a structured envelope. It doesn't mention auth or rate limits, but the behavior is well-described.

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

Conciseness4/5

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

The description is structured with a summary then details, but includes some jargon ('httpRequestsAdaptiveGroups') that could be simplified. It is concise but informative.

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 complexity (5 parameters, no annotations, output schema exists), the description is complete. It explains the operation, parameter semantics, and return structure, enabling an agent to use it effectively.

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 description adds significant meaning beyond the input schema, which only has titles. It explains each parameter (zone_id, match_path, attack_since/until, baseline_lookback_days) and provides context for usage.

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's purpose: 'Compare attack-window traffic vs a prior baseline window on the same path.' It uses a specific verb ('Compare') and resource ('traffic vs baseline') and distinguishes from siblings, which are primarily list/query tools.

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 explains the tool is suitable for the ATK archetype workflow and mentions the underlying queries. It does not explicitly state when not to use it, but the distinction from siblings 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