vps-mcp

Official

by vpsdotorg

Overview Schema Source Related Servers Discussions Admin

Python

Remote

server_power

Start, stop, restart, or hard stop a VPS server using its UUID.

Instructions

Control the power state of a VPS server.

Args: server_uuid: The UUID of the server action: Power action — one of: "start", "stop", "restart", "hard_stop"

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>",
      "action": "<action>"
    },
    "name": "server_power"
  }
}

Input Schema

Name	Required	Description	Default
`server_uuid`	Yes
`action`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 13, 2026

TDQS

A4/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'control the power state' without mentioning potential destructiveness (e.g., hard_stop may cause data loss), authentication needs, or rate limits.

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?

The description is extremely concise with two lines plus an argument list, all front-loaded. No unnecessary words.

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

Completeness4/5

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

Given the tool's simplicity and the presence of an output schema (not shown but indicated), the description covers the essential information. It could mention side effects or state transitions, but it is largely adequate.

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%, so the description must add meaning. It explains 'server_uuid' as the server's UUID and 'action' with explicit allowed values, compensating for the schema's lack of details.

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 'Control the power state of a VPS server,' using a specific verb and resource. It is distinct from sibling tools like create_server or delete_server, which focus on lifecycle management.

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 lists valid actions ('start', 'stop', 'restart', 'hard_stop') and defines the two parameters. However, it does not indicate when to use this tool vs alternatives, nor does it mention prerequisites like server existence.

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