Skip to main content
Glama

cf_query_http_requests_grouped

Group HTTP request analytics by dimensions like path or status to analyze traffic patterns over a time window, with optional filters and pagination.

Instructions

Group HTTP request analytics by chosen dimensions over a time window.

Calls: POST /graphql, httpRequestsAdaptiveGroups dataset.

Args:
    zone_id: zone tag.
    since, until: ISO-8601 time range.
    group_by: dimensions from _HTTP_GROUP_DIMENSIONS.
    filters: extra terms (e.g. {'edgeResponseStatus': 403,
        'clientRequestPath': '/oauth/token'}).
    limit: page size [1, 500].
    cursor: continuation token.

The grouped HTTP dataset also includes a `sum { visits, edgeResponseBytes }`
aggregate block when bytes/visit dimensions aren't already in group_by.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_idYes
sinceYes
untilYes
group_byYes
filtersNo
limitNo
cursorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so description carries full burden. It discloses the API call (POST /graphql), dataset, pagination, and aggregate behavior but does not explicitly state that the operation is read-only or mention any rate limits, authentication, or error handling.

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?

Description is concise (about 10 lines), well-structured with a clear purpose line, API call, parameter list, behavioral note, and return format. No unnecessary words.

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

Completeness4/5

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

Given no annotations and the presence of an output schema, the description covers input params, aggregate caveats, and return envelope. It could mention that zone_id must be obtained from another tool (e.g., cf_list_zones) or clarify error handling, but overall it is comprehensive.

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?

Input schema has 0% description coverage, but the description fully explains all 7 parameters: zone_id, since/until (ISO-8601), group_by (valid dimensions), filters (with example), limit (range 1-500), and cursor (pagination). This adds essential meaning beyond the schema.

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?

Description clearly states verb 'Group' and resource 'HTTP request analytics', and specifies grouping over a time window. It distinguishes itself from sibling cf_query_http_requests_raw by focusing on grouped analytics.

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

Usage Guidelines3/5

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

Description does not explicitly state when to use this tool versus alternatives like cf_query_http_requests_raw. Usage is implied but lacks clear when-to-use or when-not-to-use guidance.

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