Skip to main content
Glama
Sign In
cloudflare-mcp

cloudflare-mcp

by jimsimoy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_zone

Retrieve a Cloudflare zone's details by its zone ID. Get configuration, status, and metadata for a specific zone to manage DNS records.

Instructions

Fetch one zone's details by its Cloudflare zone ID.

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

Input Schema

NameRequiredDescriptionDefault
zone_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It says 'Fetch' which implies a read operation, but does not disclose error handling, authentication requirements, or what 'details' specifically includes. The output schema covers return shape, but the description adds little beyond the basic read semantics.

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?

One concise sentence, front-loaded with the verb and resource, with no filler. Every word contributes to the core meaning.

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 simple read tool with one parameter and an output schema, the description is largely sufficient. It does not cover error cases or explicit usage exclusions, but the tool's simplicity and the presence of an output schema mitigate the gap. The missing guidance about list_zones is a minor deficiency.

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 schema provides only a title ('Zone Id') with 0% description coverage. The description clarifies that the parameter is specifically the Cloudflare zone ID, which disambiguates from other ID types. This is meaningful added value for the single parameter.

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?

Description states a clear verb ('Fetch'), a specific resource ('one zone's details'), and the identifying mechanism ('by its Cloudflare zone ID'). It clearly differentiates from siblings like list_zones (which lists zones) and DNS record tools by specifying it targets a single zone.

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 indicates this is for fetching a single zone when an ID is known, as opposed to list_zones for enumeration. However, it does not explicitly name the alternative or state when NOT to use it, leaving some inference to the agent.

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