Skip to main content
Glama

Delete VPS backup

vps_delete_backup
Destructive

Delete a VPS backup for good and free its backup slot. It cannot be undone: take the backupId from vps_list_backups and keep at least one recent backup before risky work. To roll the VPS back instead, use vps_restore_backup. 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_delete_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
confirmYesMust be true to confirm deletion
backupIdYesbackupId from vps_list_backups

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes further by stating the deletion is permanent and irreversible, that the backup slot is freed, and that confirm must be true. That is concrete side-effect disclosure beyond the structured fields, which is exactly what a destructive tool needs.

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 and irreversibility front-loaded, followed by the ID provenance and the alternative tool. No filler or redundant phrasing.

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 a 3-parameter destructive tool with no output schema, the definition covers what it does, where the ID comes from, the confirmation gate, and the safer alternative. Nothing an agent needs before invoking it is missing.

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%, and the schema itself already documents all three parameters, including that backupId comes from vps_list_backups and that confirm must be true. The description restates those points rather than adding new meaning (formats, constraints, edge cases), so the baseline of 3 applies.

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?

The description opens with a specific verb and resource ('Delete a VPS backup') plus the consequence ('free its backup slot'), which cleanly separates it from vps_create_backup, vps_list_backups, and vps_restore_backup. An agent can identify the tool's job without inspecting the schema.

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?

It gives explicit routing: take backupId from vps_list_backups, use vps_restore_backup if the goal is a rollback, and set confirm=true. It also adds a safety precondition (keep at least one recent backup before risky work), covering when to use and when to prefer an alternative.

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.