@kodim/mcp-cloudflare-dns

Get DNS Analytics

get_dns_analytics

Read-only

Retrieve a DNS query analytics summary for a zone, covering query count, response times, and cache performance over a specified period.

Instructions

Get DNS query analytics summary for a zone. Returns aggregate metrics like query count, response times, and cache performance over a time period.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "zone_id": "<zone_id>"
    },
    "name": "get_dns_analytics"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort metrics (prefix with - for descending, e.g., -queryCount)
`limit`	No	Maximum number of rows to return
`since`	No	Start time in ISO 8601 format (e.g., 2024-01-01T00:00:00Z)
`until`	No	End time in ISO 8601 format
`filters`	No	Filters in Cloudflare analytics filter format (e.g., queryType==A)
`metrics`	No	Metrics to return (default: all). Options: queryCount, uncachedCount, staleCount, responseTimeAvg, responseTimeMedian, responseTime90th, responseTime99th
`zone_id`	Yes	The zone ID
`dimensions`	No	Dimensions to group by. Options: queryName, queryType, responseCode, responseCached, coloName, origin

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds context about what the tool returns: aggregate metrics like query count, response times, and cache performance over a time period. This is consistent with the annotations and provides additional behavioral insight without contradicting them.

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 a single, front-loaded sentence with no extraneous words. It efficiently covers the purpose, scope, and primary return content, earning its place in concise structuring.

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

Completeness3/5

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

With 8 parameters and no output schema, the description is somewhat minimal. It gives a high-level summary but fails to mention that specifying dimensions (e.g., queryName, coloName) will produce multiple grouped rows, nor does it describe the response structure. This gap is notable for a complex analytics tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents all parameters. The description only loosely references the time period (since/until) but does not add meaning beyond what the schema provides. Hence, the baseline score of 3 applies.

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 gets a DNS query analytics summary for a zone, using the specific verb 'Get' and resource 'DNS query analytics summary.' It also mentions aggregate metrics like query count, response times, and cache performance, which effectively distinguishes it from the sibling tool get_dns_analytics_by_time that focuses on time-series breakdowns.

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 implicitly conveys that this tool is for aggregate summaries over a time period, not for time-series drill-downs. However, it does not explicitly name an alternative tool for time-series needs or include clear 'when-not-to-use' guidance, so it falls short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server