@kodim/mcp-cloudflare-dns

Get DNS Analytics by Time

get_dns_analytics_by_time

Read-only

Retrieve DNS analytics grouped by time intervals to track trends, spot patterns, and monitor metric changes over time.

Instructions

Get DNS analytics broken down by time intervals. Returns time-series data for DNS metrics. Useful for monitoring trends and identifying patterns.

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

Input Schema

Name	Required	Description
`sort`	No	Sort metrics
`limit`	No	Maximum rows to return
`since`	No	Start time in ISO 8601 format
`until`	No	End time in ISO 8601 format
`filters`	No	Filters in Cloudflare analytics filter format
`metrics`	No	Metrics to return (default: all)
`zone_id`	Yes	The zone ID
`dimensions`	No	Dimensions to group by
`time_delta`	No	Time interval for grouping data (default: auto)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that the tool returns 'time-series data' and groups by 'time intervals,' which is useful behavioral context. It does not mention pagination, limits, or default metrics/aggregation behavior, but the annotation lowers the burden.

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 short sentences, front-loaded with the core purpose. Every sentence adds value: what it does, what it returns, and when it's useful. No fluff or repetition.

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 9 parameters, no output schema, and a sibling `get_dns_analytics`, the description gives the essential idea but lacks explicit differentiation from the sibling. It explains why one would use this tool (trends/patterns) but does not mention how it interacts with parameters like `metrics` or `time_delta`. Given full schema coverage, the description is adequate but not fully complete for tool selection.

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 each parameter is already documented in the schema. The description does not add parameter-level meaning beyond stating that data is broken down by time intervals, which aligns with `time_delta` but provides no extra syntax or defaults.

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 states a specific verb ('Get') and resource ('DNS analytics') with a clear scope ('broken down by time intervals'). It distinguishes from the sibling tool `get_dns_analytics` by emphasizing the time-series aspect, though it does not explicitly name or compare with that sibling.

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 description says 'Useful for monitoring trends and identifying patterns,' which conveys a clear use case. However, it does not provide explicit alternatives or when-not-to-use guidance, especially given the sibling `get_dns_analytics` that may differ only in time grouping.

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

Deploy Server