Skip to main content
Glama

Upgrade VPS

vps_upgrade
Destructive

Upgrade VPS resources (CPU, RAM, disk, backup slots, network speed). Only upgrades are allowed -- values must be >= current. Creates a pro-rated payment via your saved mandate; infrastructure changes are applied after payment confirmation. You MUST set confirm to true.

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": {
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "vps_upgrade"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
memNoNew RAM in GB (must be >= current)
diskNoNew NVMe disk in GB (must be >= current)
coresNoNew CPU core count (must be >= current)
confirmYesMust be true to confirm this billable operation
storageNoNew HDD storage in GB (must be >= current)
backupSlotsNoNew backup slot count (must be >= current)
networkSpeedNoNew network speed in Mbit/s (must be >= current)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description adds genuinely useful context beyond that — this is a billable, pro-rated charge through a saved mandate and takes effect only after payment confirmation. It does not say what happens if payment fails, whether a failed payment leaves the VPS untouched, or whether the operation is reversible.

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?

Four short sentences, front-loaded with the resource scope, then the constraint, then the billing/timing behavior, then the hard requirement. No filler and nothing an agent needs is buried.

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?

For a billable mutation with no output schema, the description covers cost, timing, and the confirm gate well. It could go further on failure semantics (payment declined, partial application) and on how to discover current values before upgrading, but the essentials are present.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter (including confirm, id, and the >= current constraints) is already documented in the schema. The description repeats the upgradable fields and the >= current rule without adding format, units, or defaults beyond what the schema supplies, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Upgrade) and resource (VPS) and enumerates the upgradable dimensions (CPU, RAM, disk, backup slots, network speed), which differentiates it from vps_create and vps_reinstall_os. It does not explicitly route to the sibling webspace_upgrade for a different resource type, but the resource noun in the name makes the boundary reasonably clear.

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?

Gives concrete preconditions: only upgrades are permitted, new values must be >= current, and confirm must be true. It also explains the ordering (payment confirmation precedes infrastructure change). It lacks an explicit statement of when an agent should choose a different tool, e.g. that downgrades are not possible here at all.

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.