Skip to main content
Glama

Restore VPS backup

vps_restore_backup
Destructive

Restore a backup on a VPS. WARNING: This will overwrite current 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>",
      "backupId": "<backupId>",
      "confirm": "<confirm>"
    },
    "name": "vps_restore_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
confirmYesMust be true to confirm this destructive operation
backupIdYesThe backup ID to restore

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 flag destructiveHint=true and readOnlyHint=false, so the bar is lower, but the description adds real specificity: it names what is destroyed ('current data') and mandates a confirmation flag. It still doesn't say whether the VPS is rebooted or made unavailable during the restore, or whether the action 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?

Three short sentences: purpose first, then the destructive warning, then the hard requirement. Every sentence carries actionable information with no filler.

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?

With only three fully documented required parameters, annotations covering the safety profile, and no output schema, the description covers the essentials an agent needs to call it safely. Remaining gaps are operational details like post-restore state and synchronization behavior.

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%, including the ID pattern and the confirm flag semantics, so the schema carries all parameter meaning. The description adds nothing about the id/backupId/confirm parameters beyond restating the confirm requirement.

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 (restore) applied to a specific resource (backup on a VPS), which is naturally distinguishable from the create/delete/list backup siblings. It does not explicitly name an alternative, but the operation is unambiguous.

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 destructive warning and the confirm=true requirement imply this is the tool for rolling back to a backup, but it never states prerequisites (e.g., obtaining a backupId via vps_list_backups) or when to prefer reinstall_os over restore. Usage is implied rather than spelled out.

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.