mcp-server-cloudflare

cf_dns_list

Retrieve DNS records for a Cloudflare zone to manage domain configurations and troubleshoot connectivity issues.

Instructions

List DNS records for a zone

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": {
      "zoneId": "<zoneId>"
    },
    "name": "cf_dns_list"
  }
}

Input Schema

Name	Required	Description
`zoneId`	Yes	Zone ID
`page`	No	Page
`perPage`	No	Per page

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't mention pagination details (implied by 'page' and 'perPage' parameters), rate limits, authentication requirements, or error handling, which are critical for safe and effective use.

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, efficient sentence that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

Given the complexity of a list operation with pagination and no output schema, the description is incomplete. It lacks details on return values (e.g., record format), error cases, or how to handle multiple pages, which are essential for an agent to use the tool correctly in a real-world context.

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 schema fully documents parameters like 'zoneId', 'page', and 'perPage'. The description adds no additional meaning beyond the schema, such as explaining what a 'zoneId' represents or how pagination works in practice, resulting in a baseline score.

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 clearly states the action ('List') and resource ('DNS records for a zone'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'cf_dns_create' or 'cf_dns_delete' beyond the basic verb, which would require more specificity for a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. For example, it doesn't mention when to choose this over 'cf_kv_keys' for key-value operations or 'cf_zones' for zone management, leaving the agent to infer usage from tool names alone.

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

Deploy Server