Skip to main content
Glama

Order VPS

vps_create
Destructive

Create a new VPS. Creates an order, charges your saved payment method, and provisions the server. Returns the order ID to track progress via get_order_status. You MUST set confirm to true.

Discovery: call vps_get_pricing (no args) to enumerate valid hostsystem identifiers and the min/max ranges for cores/mem/disk per hostsystem. The OS list is hostsystem-specific; common values are 'ubuntu-24.04', 'ubuntu-22.04', 'debian-12'.

Use vps_get_pricing with hostsystem + resource amounts to preview the monthly/yearly cost before committing.

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": {
      "hostsystem": "<hostsystem>",
      "os": "<os>",
      "cores": "<cores>",
      "mem": "<mem>",
      "disk": "<disk>",
      "confirm": "<confirm>"
    },
    "name": "vps_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
osYesOperating system identifier (e.g. 'ubuntu-24.04', 'debian-12')
ipsNoNumber of IPv4 addresses (default: 1)
memYesRAM in GB (e.g. 8)
diskYesNVMe disk in GB (e.g. 20)
nameNoDisplay name for the VPS (optional)
coresYesNumber of CPU cores
confirmYesMust be true to confirm this billable operation
storageNoAdditional HDD storage in GB (optional)
hostsystemYesHost system identifier (e.g. 'de_epyc', 'de_ryzen'). Discover valid values via vps_get_pricing.
backupSlotsNoNumber of backup slots (default: 2)
networkSpeedNoNetwork speed in Mbit/s (default: 1000)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Going beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses the concrete consequence the annotations only imply: a real charge to the saved payment method and server provisioning. It also tells the agent what is returned (order ID) and how to follow up on it.

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?

Front-loaded with the action and its billing consequence, then the discovery and preview instructions in compact labeled paragraphs. The repeated `vps_get_pricing` guidance (enumeration vs. cost preview) is slightly redundant but not wasteful.

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

Completeness5/5

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

For an 11-parameter, 6-required, billable mutation with no output schema, the description covers the whole decision path: discover valid hostsystem, preview cost, commit with confirm, then track via order ID. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the baseline is 3; the description earns above that by explaining where valid hostsystem values come from, that the OS list is hostsystem-specific, and that resource ranges vary per hostsystem. It stops short of describing defaults for the optional parameters, which the schema already covers.

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?

Specific verb and resource ('Create a new VPS') followed by the concrete side effects: creates an order, charges the saved payment method, provisions the server. This is clearly distinguishable from siblings like vps_get, vps_cancel, or vps_get_pricing.

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

Usage Guidelines5/5

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

Explicitly states the prerequisite discovery step (call vps_get_pricing with no args to enumerate valid hostsystem values and min/max ranges), the preview workflow before committing, and the alternative tracking tool (get_order_status). It also states the mandatory 'confirm' requirement, leaving little to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.