cargoshipper-mcp

by scarr7981

Overview Schema Source Related Servers Discussions Admin

Python

Local

cf_create_zone

Creates a new CloudFlare zone for a domain, specifying account and zone type. Optionally imports existing DNS records.

Instructions

Create a new CloudFlare zone

Args: name: Domain name for the zone account_id: CloudFlare account ID jump_start: Import existing DNS records automatically zone_type: Zone type ('full' or 'partial')

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": {
      "name": "<name>",
      "account_id": "<account_id>"
    },
    "name": "cf_create_zone"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`account_id`	Yes
`jump_start`	No
`zone_type`	No	full

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 26, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, and description omits behavioral traits such as permission requirements, zone initialization states, or rate limits. The mutation intent is clear but insufficient disclosure.

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?

Description is brief (6 lines) and uses a clear 'Args:' structure. No wasted words, though could be slightly more organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers basic creation purpose and parameters, but lacks usage context and behavioral details. Output schema exists (not shown), so return value explanation is forgivable. Incomplete for a 4-param creation tool.

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?

Schema has 0% description coverage, but the description compensates by explaining each parameter: 'name' as domain name, 'account_id' as account ID, 'jump_start' for auto-import, and 'zone_type' with allowed values ('full' or 'partial'). Adds meaning beyond schema titles.

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?

The description clearly states 'Create a new CloudFlare zone', specifying the verb and resource. It distinguishes from siblings like cf_delete_zone and cf_get_zone. However, it could elaborate on what a zone represents (e.g., domain).

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?

No guidance on when to use this tool versus alternatives, or any prerequisites (e.g., domain verification). Lacks explicit context for appropriate usage.

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