Skip to main content
Glama
Sign In
MCP Cloudflare DNS Server

MCP Cloudflare DNS Server

by neverprepared
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_zones

List all Cloudflare domains on your account to find the zone ID for any domain name.

Instructions

List all Cloudflare zones (domains) on the account. Use this to discover zone IDs when the user refers to a domain by name.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

A4.2/5.0
Behavior3/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 clearly indicates this is a read-only listing operation with account-wide scope, but it does not mention pagination, response structure, or ordering behavior, which are minor for such a simple tool.

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 two concise sentences with no filler. The primary action and resource are front-loaded, followed by a clear usage hint. Every word earns its place.

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?

For a zero-parameter list tool with no output schema, the description adequately explains what the tool returns (zones with IDs) and when to use it. The only small gap is lack of detail on the exact response shape, but the stated purpose makes the output predictable enough for an agent.

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?

The input schema has zero parameters and 100% schema description coverage, so there is no parameter information to add. Per the rubric, a zero-parameter tool earns a baseline of 4, and the description correctly does not invent parameter guidance.

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 states a specific verb ('List') and resource ('all Cloudflare zones (domains) on the account'), making the tool's scope immediately clear. It also explains its main purpose—discovering zone IDs from a domain name—which distinguishes it from the sibling DNS record tools that operate on records, not zones.

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 explicitly gives a usage condition: use this when the user refers to a domain by name and you need its zone ID. It does not mention when not to use it or name alternative tools, but the provided guidance is clear enough for routing.

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