vps-mcp

Official

by vpsdotorg

Overview Schema Source Related Servers Discussions Admin

Python

Remote

delete_dns_record

Delete a DNS record by its UUID to remove it from your domain's DNS configuration.

Instructions

Delete a DNS record.

Args: record_uuid: The UUID of the DNS record 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": {
      "record_uuid": "<record_uuid>"
    },
    "name": "delete_dns_record"
  }
}

Input Schema

Name	Required	Description	Default
`record_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

C2.8/5.0

Behavior2/5

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

Without annotations, the description carries the full burden. It indicates a destructive action ('delete') but does not disclose behavioral traits like irreversibility, confirmation requirements, or side effects (e.g., propagation time). The parameter list adds no behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (one sentence plus an arg list) but the arg list is redundant with the input schema. It is front-loaded with the action, but some information is unnecessary. It is adequately concise but could be streamlined.

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 tool's simplicity (one parameter) and presence of an output schema, the description covers the basic purpose. However, it lacks details about deletion behavior (e.g., permanent, cascading effects). For a simple operation, it is minimally complete but leaves gaps for an agent.

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

Parameters1/5

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

With 0% schema description coverage, the description must add meaning to the parameter, but it only repeats the parameter name 'record_uuid' without explaining its role or format. The schema already provides the type as string, so no semantic value is added.

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 'Delete a DNS record' clearly states the action (delete) and the resource (DNS record). It distinguishes from sibling tools like create_dns_record and delete_dns_zone, which operate on different verbs or resources.

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. There is no mention of prerequisites, such as whether the record must exist or if deletion is irreversible. This lack of context leaves the agent to infer usage from the tool name alone.

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