Skip to main content
Glama
Sign In
domain-manager-mcp

domain-manager-mcp

by WangJiyuanYo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_dns

Remove exactly one DNS record from Cloudflare after a dry-run check and explicit confirmation, ensuring safe, precise deletion.

Instructions

Delete exactly one DNS record. confirm_delete must be true; prefer dry_run first.

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": {
      "type": "<type>",
      "name": "<name>",
      "confirm_delete": "<confirm_delete>"
    },
    "name": "delete_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
typeYes
dry_runNo
allow_rootNo
confirm_deleteYes
allow_sensitiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well by disclosing the destructive nature, requiring confirm_delete, and recommending dry_run as a safety step. It does not describe what dry_run actually does or the permanence of deletion, but the core behavioral safeguards are present.

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?

Two concise sentences with no filler. The core action is front-loaded and the safety requirements follow immediately. Every word earns its place.

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

Completeness2/5

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

For a destructive tool with no annotations and no output schema, the description is incomplete. It omits the meaning of allow_root and allow_sensitive, the role of name and type, and what happens when dry_run is true or when no matching record exists. These gaps could lead an agent to misuse the tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only adds meaning for confirm_delete and dry_run, while name, type, allow_root, and allow_sensitive remain unexplained. These are critical for correct invocation, especially the safety-related flags.

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 states a specific action ('Delete exactly one DNS record') with a clear resource and an explicit scope ('exactly one'). This distinguishes it from create, update, upsert, and list operations without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear operational guidance: confirm_delete must be true and dry_run should be preferred first. It does not explicitly name alternative tools or conditions for using them, but the delete operation is naturally distinct from its siblings.

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