cargoshipper-mcp

Overview Schema Source Related Servers Discussions Admin

cf_create_dns_record

Create a DNS record in a CloudFlare zone, supporting A, AAAA, CNAME, MX, TXT types, with configurable TTL, proxied status, and MX priority.

Instructions

Create a DNS record

Args: zone_id: CloudFlare zone ID record_type: DNS record type (A, AAAA, CNAME, MX, TXT, etc.) name: Record name (subdomain or @ for root) content: Record content (IP address, domain name, etc.) ttl: Time to live (1 = Auto, 120-7200 seconds) proxied: Whether to proxy through CloudFlare (orange cloud) priority: Priority for MX records

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>",
      "record_type": "<record_type>",
      "name": "<name>",
      "content": "<content>"
    },
    "name": "cf_create_dns_record"
  }
}

Input Schema

Name	Required	Description	Default
`zone_id`	Yes
`record_type`	Yes
`name`	Yes
`content`	Yes
`ttl`	No
`proxied`	No
`priority`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses that the tool creates a record and explains parameters like proxied and ttl, which imply behavior. However, it does not mention error handling, idempotency, or what happens if the record already exists, leaving gaps for an agent.

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 structured as a clear list with an opening statement, front-loading the purpose. It is concise enough, though the parameter list could be slightly more terse. No redundant sentences.

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?

Given the existence of an output schema, the description does not need to cover return values. It thoroughly explains all 7 parameters. However, it lacks context on failure modes, duplicate handling, and dependencies (e.g., zone existence), which are relevant for a 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?

The input schema has no descriptions (0% coverage), so the description is the sole source. It explains each parameter with meaningful details (e.g., 'TTL: Time to live (1 = Auto, 120-7200 seconds)', 'priority: Priority for MX records'), adding significant value beyond the schema's type and 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?

The description explicitly states 'Create a DNS record', matching the tool name and clearly indicating a creation action. It is distinct from sibling tools like cf_update_dns_record and cf_delete_dns_record, making the tool's purpose unambiguous.

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 is provided on when to use this tool versus alternatives. While its purpose is clear, there is no mention of prerequisites (e.g., zone must exist) or situations where updating or deleting is more appropriate, leaving the agent without decision context.

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