Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cloudflare: Get zone

cloudflare_get_zone
Read-only

Fetch one Cloudflare zone by ID to retrieve its name servers, status, plan, SSL, and security settings.

Instructions

[UNIFIED] Fetch one Cloudflare zone by id — full details including name servers, status, plan, SSL and security settings.

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": {
      "site": "<site>",
      "zone_id": "<zone_id>"
    },
    "name": "cloudflare_get_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
zone_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.9/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 useful content about what a successful response contains (name servers, status, plan, SSL and security settings), but says nothing about permissions, errors, or behavior when the zone is absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tightly written sentence with the verb-and-resource front-loaded and no padding. The unexplained "[UNIFIED]" prefix is the one piece of non-earning text, and the dash clause is informative rather than redundant.

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?

For a two-required-parameter tool with zero schema description coverage and no output schema, the definition is too thin: the `site` parameter is entirely unexplained, and there is no guidance on obtaining or validating zone_id. Given the simplicity of the operation it is usable, but not complete.

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

Parameters2/5

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

Schema description coverage is 0% for 2 parameters. The description clarifies zone_id only as "by id"; the required `site` parameter is never mentioned, so its meaning and expected format (account name, hostname, credential key?) are undocumented in both the schema and the description.

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?

Specific verb and resource: "Fetch one Cloudflare zone by id", scoped to a single record, with an enumeration of the returned fields (name servers, status, plan, SSL, security settings). This implicitly separates it from cloudflare_list_zones, though no sibling is named explicitly.

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?

There is no when-to-use guidance, no stated prerequisites, and no pointer to where a zone_id comes from (e.g. cloudflare_list_zones). The phrase "by id" hints that an identifier must already be known, but the agent must infer that.

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