Skip to main content
Glama
wojtekkura

cf-mcp

by wojtekkura
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

cf_get_zone

Retrieve complete details of a Cloudflare zone including plan, name servers, settings summary, and status by providing a zone ID.

Instructions

Get full details for one zone (plan, name servers, settings summary, status).

Args:
    zone_id: 32-char Cloudflare zone ID.

Calls: GET /zones/{zone_id}.

Allowlist enforcement runs AFTER the API call (we need the zone name to
check against the list). If the zone is outside the allowlist, returns
`zone_not_allowed` error — but a CF quota call has been spent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

Discloses that allowlist enforcement runs after API call, wasting a CF quota even on disallowed zones. Also specifies the API endpoint and return summary. Annotations are absent so description carries full burden; this is well done.

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?

Description is extremely concise: three lines cover purpose, parameters, API call, and behavioral note. No wasted words.

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?

Given the existence of an output schema, the description appropriately summarizes return data without exhaustive field listing. Includes allowlist behavior and quota cost, which is important context 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?

With 0% schema description coverage, the description adds '32-char Cloudflare zone ID' for the zone_id parameter, providing format and context beyond the schema's 'Zone Id' title.

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 clearly states 'Get full details for one zone' and lists specific contents (plan, name servers, settings summary, status). Distinguishes from sibling cf_list_zones (list all) and cf_resolve_zone (resolve name to ID).

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?

No explicit guidance on when to use this tool vs alternatives (e.g., cf_list_zones for enumeration, cf_resolve_zone for name lookup). Usage is implied but not stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wojtekkura/cf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server