Skip to main content
Glama
Sign In
cargoshipper-mcp

cargoshipper-mcp

by scarr7981
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cf_delete_dns_record

Delete a specific DNS record from a Cloudflare zone by providing the zone ID and record ID.

Instructions

Delete a DNS record

Args: zone_id: CloudFlare zone ID record_id: DNS record ID

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_id": "<record_id>"
    },
    "name": "cf_delete_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
zone_idYes
record_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/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 indicates deletion is destructive but does not disclose side effects, permissions, or reversibility. There is no mention of error conditions or idempotency.

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 concise with one sentence for purpose and clear parameter mapping under 'Args:'. No wasted words, though it could be more front-loaded by putting the purpose first.

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?

For a simple delete operation, the description provides minimal context. It does not explain the output schema or error conditions. While the tool is straightforward, there is room for improvement in providing complete guidance.

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 description coverage is 0%, but the description adds meaning by defining 'zone_id' as 'CloudFlare zone ID' and 'record_id' as 'DNS record ID', which the schema's titles lack. This compensates for the low coverage.

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 'Delete a DNS record', which is a specific verb and resource. It distinguishes from sibling tools like cf_create_dns_record and cf_update_dns_record.

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 such as cf_update_dns_record or cf_list_dns_records. No exclusions or context provided.

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