vps-mcp

Official

by vpsdotorg

Overview Schema Source Related Servers Discussions Admin

Python

Remote

delete_dns_zone

Delete a DNS zone and all its records. Provide the zone UUID to remove the zone and associated data.

Instructions

Delete a DNS zone and all its records.

Args: zone_uuid: The UUID of the DNS zone to delete

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_uuid": "<zone_uuid>"
    },
    "name": "delete_dns_zone"
  }
}

Input Schema

Name	Required	Description	Default
`zone_uuid`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It notes the destructive nature but lacks details on irreversibility, permissions needed, or what happens if the zone doesn't exist. Minimal behavioral 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?

The description is extremely short and front-loaded with the essential action. However, the parameter docstring could be integrated better. No wasted words, but slightly under-specified.

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?

While an output schema exists, its contents are not visible. The description does not mention return values, error states, or side effects beyond deletion. For a destructive operation, more context is expected.

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?

The input schema has one required parameter (zone_uuid) with 0% schema description coverage. The tool description adds 'The UUID of the DNS zone to delete', which essentially restates the parameter name and provides negligible additional meaning beyond the 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 'Delete a DNS zone and all its records', using a specific verb and resource. It distinguishes itself from sibling tools like delete_dns_record which only deletes a single record.

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 implies that this tool is for completely removing a zone and its records, but it does not explicitly state when to use it vs alternatives like delete_dns_record, or provide any prerequisites or conditions.

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