Skip to main content
Glama
Sign In
mcp-cloudflare-crunchtools

mcp-cloudflare-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Zone Analytics Tool

get_zone_analytics_tool
Read-only

Retrieve Cloudflare zone traffic analytics for a date range: total requests, unique visitors, bandwidth, cache ratio, and status code breakdown. Specify zone_id or zone_name.

Instructions

Get zone traffic analytics summary.

Returns total requests, unique visitors, bandwidth, cache ratio, and status code breakdown for the given date range.

Provide either zone_id or zone_name, not both.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoStart date ISO format (default: 30 days ago)
untilNoEnd date ISO format (default: today)
zone_idNoZone ID (32-character hex string)
zone_nameNoZone name (domain like example.com)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / since / description
      Added value: +"Start date ISO format (default: 30 days ago)"
    • addedInput schema / properties / until / description
      Added value: +"End date ISO format (default: today)"
    • addedInput schema / properties / zone_id / description
      Added value: +"Zone ID (32-character hex string)"
    • addedInput schema / properties / zone_name / description
      Added value: +"Zone name (domain like example.com)"
  2. Changed5 schema fields changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / since / description
      Removed value: -"Start date ISO format (default: 30 days ago)"
    • removedInput schema / properties / until / description
      Removed value: -"End date ISO format (default: today)"
    • removedInput schema / properties / zone_id / description
      Removed value: -"Zone ID (32-character hex string)"
    • removedInput schema / properties / zone_name / description
      Removed value: -"Zone name (domain like example.com)"
  3. First observedv0.5.0

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true already declares this as a safe read, so the description only needs to add context. It reinforces the read-only summary nature and adds the zone exclusivity rule, but says nothing about auth requirements, rate limits, or the timezone/aggregation behavior of the date range.

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?

Three tight lines, front-loaded with the purpose, then return contents, then the one invocation caveat. No filler or repetition.

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?

With an output schema present, the field list is arguably redundant but harmless, and the exclusivity rule covers the main ambiguity. The only remaining gap is guidance on default behavior when no zone is supplied, which is minor given all four parameters are optional and documented.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds a genuine constraint the schema does not express: zone_id and zone_name are mutually exclusive. That is real added meaning beyond the structured fields.

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?

States a specific verb and resource — 'Get zone traffic analytics summary' — and enumerates what the summary contains (requests, visitors, bandwidth, cache ratio, status codes). It is clear what the tool returns, though it never names the sibling analytics tools (get_top_pages_tool, get_traffic_by_country_tool) that an agent might confuse it with.

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?

The 'Provide either zone_id or zone_name, not both' line gives an invocation constraint, which is useful. However, it says nothing about when to pick this tool over the other analytics siblings, or what happens if no zone is supplied (all params are optional and defaulted).

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