vps-mcp

Official

by vpsdotorg

Overview Schema Source Related Servers Discussions Admin

Python

Remote

delete_server

Permanently remove a VPS server by providing its UUID. This irreversible action deletes the server instantly.

Instructions

Permanently delete a VPS server. This action is irreversible.

Args: server_uuid: The UUID of the server 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": {
      "server_uuid": "<server_uuid>"
    },
    "name": "delete_server"
  }
}

Input Schema

Name	Required	Description	Default
`server_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/5.0

Behavior3/5

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

The description highlights irreversibility, which is a critical behavioral trait. However, with no annotations, it does not fully disclose consequences (e.g., whether associated resources like IPs or backups are affected) or any required states (e.g., server must be stopped). The warning is useful but incomplete.

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 brief and front-loaded with the key purpose and irreversibility. The Args section is slightly redundant with the schema but does not detract significantly. Every sentence serves a purpose, though it could omit the Args section entirely.

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 action with no annotations, the description omits important context like error scenarios, prerequisites, or side effects. Even though an output schema exists, the agent lacks guidance on what to expect after deletion or how to handle errors.

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?

The description restates the schema parameter 'server_uuid' without adding any context about its format, constraints, or how to obtain it. With 0% schema description coverage, this fails to add meaningful value 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 the action: 'Permanently delete a VPS server.' It uses a specific verb ('delete') and resource ('server'), and the irreversibility warning distinguishes it from non-destructive sibling tools like create_server or resize_server.

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 (e.g., when to power down instead). The description does not mention any prerequisites, conditions, or exclusions, leaving the agent to infer usage context.

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