Skip to main content
Glama

Reinstall a machine

reinstall_vm
Destructive

ERASES THE DISK and redeploys another image. Ask the user first. confirm_hostname must be the machine's exact current hostname. Scope: vms.action.

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": {
      "vm": "<vm>",
      "image": "<image>",
      "confirm_hostname": "<confirm_hostname>"
    },
    "name": "reinstall_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
vmYesMachine id, as returned by list_vms or create_vm.
imageYesImage slug from list_images, offered in the machine's region and fitting its plan.
ssh_keysNoFingerprints or ids of SSH keys already on the account (see list_ssh_keys) to install on the new system.
confirm_hostnameYesThe machine's exact hostname, typed back as confirmation.
password_deliveryNoemail (default) mails a generated password; none needs at least one SSH key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / password_delivery / description
      Added value: +"email (default) mails a generated password; none needs at least one SSH key."
    • addedInput schema / properties / ssh_keys / description
      Added value: +"Fingerprints or ids of SSH keys already on the account (see list_ssh_keys) to install on the new system."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds concrete value beyond them by specifying exactly what is destroyed ('ERASES THE DISK') and by imposing a human-confirmation protocol. It still does not say whether data or backups survive, whether the IP changes, or how long the operation takes.

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?

Three short sentences, with the destructive warning front-loaded in capitals. Every sentence adds information: what happens, what the agent must do first, and the confirmation constraint. Nothing is wasted.

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 five-parameter destructive mutation with full schema coverage, full annotations, and no output schema, the description covers the essential risk and confirmation protocol. It is slightly thin on post-reinstall consequences (data loss beyond the disk, IP/hostname changes, downtime), which an agent or user might need before approving.

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 all five parameters are already documented. The description reinforces the safety-critical confirm_hostname requirement (exact current hostname), but that meaning is already in the schema, and it adds nothing about image, ssh_keys, or password_delivery. Baseline 3 is appropriate.

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?

The description states a specific verb and resource: it erases the disk and redeploys another image onto an existing machine. This clearly distinguishes the tool from create_vm (new machine) and destroy_vm (removal), although it does not name those siblings explicitly.

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?

It gives an explicit behavioral rule: 'Ask the user first,' which tells the agent to obtain confirmation before calling. It does not name alternatives such as create_vm or destroy_vm, so the choice among them is implied rather than stated, but the key usage constraint is present.

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.