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

mcp-cloudflare-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Traffic By Country Tool

get_traffic_by_country_tool
Read-only

Retrieve traffic breakdown by country for a Cloudflare zone, using zone ID or domain and optional date range, to analyze regional traffic patterns.

Instructions

Get traffic breakdown by country.

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_traffic_by_country_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of countries (default: 20)
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. Changed6 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / description
      Added value: +"Number of countries (default: 20)"
    • 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. Changed6 schema fields changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / limit / description
      Removed value: -"Number of countries (default: 20)"
    • 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?

The readOnlyHint annotation already establishes this is a safe read, so the description's burden is reduced. It adds the useful constraint that zone_id and zone_name are mutually exclusive, but says nothing about what happens if both are supplied, whether results are paginated, or how the breakdown is ordered.

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?

Two short sentences, purpose stated first, constraint second. No filler, no restatement of the title, nothing that could be trimmed.

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?

An output schema exists, so return values need no explanation, and the schema fully covers the five optional parameters. Only the missing sibling routing and failure behavior for conflicting zone identifiers keep it below a 5 for a five-parameter analytics tool.

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 coverage is 100%, so limit/since/until/zone_id/zone_name are all documented in the schema (baseline 3). The description adds one genuinely non-derivable rule — "provide either zone_id or zone_name, not both" — since the schema marks both as nullable and would permit supplying both.

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?

The description gives a specific verb+resource ("Get traffic breakdown by country"), which is clearly distinct from analytics siblings like get_top_pages_tool, get_security_events_tool, and get_zone_analytics_tool. It does not explicitly name or contrast with those siblings, so it stops short of a 5.

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?

Usage is only implied by the resource name plus the mutual-exclusion constraint on zone identifiers. There is no statement of when to prefer this over get_zone_analytics_tool or get_top_pages_tool, and no prerequisite guidance (e.g., that a zone must exist or that the caller needs analytics permission).

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