cargoshipper-mcp

Overview Schema Source Related Servers Discussions Admin

cf_list_zones

List CloudFlare zones with optional filters for name, status, and pagination. Retrieve zone details for management and monitoring.

Instructions

List CloudFlare zones

Args: per_page: Number of zones per page (5-50) page: Page number to retrieve
name: Filter by zone name status: Filter by status (active, pending, initializing, moved, deleted, deactivated)

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

Input Schema

Name	Required	Description	Default
`per_page`	No
`page`	No
`name`	No
`status`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 26, 2026

TDQS

A4/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 the full burden. It states the tool lists zones and describes parameters, but it does not disclose any behavioral traits like idempotency, rate limits, or authentication requirements. Since it's a read operation, this is acceptable but minimal.

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?

The description is brief and front-loaded with the purpose. The parameter list is well-structured but could be more compact. No unnecessary sentences.

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 output schema exists, the description sufficiently covers purpose and parameters. However, without annotations, it lacks behavioral context like idempotency or auth, but for a simple list tool, this is largely adequate.

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

Parameters5/5

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

Schema coverage is 0%, so the description fully explains the parameters. It provides clear semantics: per_page range (5-50), page number, name filter, and status filter with enumerated values. This adds significant value beyond the bare schema.

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 clearly states 'List CloudFlare zones' with a specific verb and resource. It is distinct from sibling tools like cf_get_zone (single zone) and cf_create_zone, ensuring no ambiguity.

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?

The description lists parameters and their purposes, implying when to use this tool (to list zones with filters). However, it lacks explicit guidance on when not to use it or alternatives, such as cf_get_zone for a single zone.

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