Skip to main content
Glama

Reinstall VPS operating system

vps_reinstall_os
Destructive

Reinstall the operating system on a VPS. WARNING: This will erase all data. 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>",
      "os": "<os>",
      "confirm": "<confirm>"
    },
    "name": "vps_reinstall_os"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
osYesThe operating system identifier to install (e.g. 'ubuntu-24.04')
confirmYesMust be true to confirm this destructive operation

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the bar is lower, but the description adds real value by spelling out the consequence ('erase all data') and the required confirm gate. It still does not mention downtime, reboot behavior, or whether the OS must be from a supported list.

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 no waste; the destructive warning and the confirm requirement are front-loaded and easy to scan.

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 three-parameter destructive tool with full schema coverage and no output schema, the definition covers consequence and confirmation adequately. Omitting downtime expectations and OS identifier validity is a small gap but worth noting for an agent planning a reinstall.

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 coverage is 100%, so the schema already documents all three parameters. The description reinforces the confirm semantics ('MUST set to true'), which is marginally useful for a gated destructive call, but adds nothing about the os identifier format beyond what the schema provides.

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 and resource ('Reinstall the operating system on a VPS'), which is unambiguous. It does not differentiate itself from nearby siblings such as vps_restore_backup or vps_mount_iso, so it falls short of a 5.

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

Usage Guidelines3/5

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

The description makes the destructive consequence explicit and mandates confirm=true, which implicitly signals caution. It gives no guidance on when to choose reinstall over alternatives like restore_backup, nor any prerequisites or exclusions.

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.