Skip to main content
Glama

Create VPS backup

vps_create_backup

Create a new backup of a VPS. Optionally set a label. Returns the backup ID. 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_create_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
labelNoOptional label for the backup
confirmYesMust be true to confirm backup creation

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 only declare readOnlyHint=false and destructiveHint=false. The description adds meaningful behavior beyond that: creation is gated behind a confirm flag, a label is optional, and the call returns a backup ID. It stops short of saying whether the backup is synchronous or how long it takes, but the added context is solid for a low-risk write.

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, each earning its place: purpose first, then the optional parameter, then the return value and the mandatory safety flag. 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?

There is no output schema, and the description compensates by stating the return value is the backup ID. For a three-parameter, non-destructive creation tool with full schema coverage, that is nearly complete; only async/latency expectations are unstated.

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 the schema already defines id, label and confirm. The description restates the optionality of label and the mandatory confirm value but adds no format or constraint detail beyond the schema. 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 opens with a specific verb+resource: 'Create a new backup of a VPS.' That is unambiguous and implicitly distinguishes it from vps_list_backups, vps_delete_backup and vps_restore_backup, though it never names 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 Guidelines3/5

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

It states a hard precondition ('You MUST set confirm to true'), which is genuine usage guidance, but it gives no when-to-use context, no prerequisites such as VPS power state, and no explicit contrast with restore/list backup tools.

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.