Skip to main content
Glama

Cancel VPS

vps_cancel
Destructive

Cancel a VPS subscription at the end of the current billing period. The VPS keeps running until the expiry date. This is a destructive operation. 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_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
confirmYesMust be true to confirm this 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 and readOnlyHint=false, so the safety profile is covered structurally. The description adds genuinely non-redundant behavior: the cancellation is deferred to period end, the VPS continues running until the expiry date, and confirm must be true. What it does not disclose is whether the pending cancellation can be undone or reverted.

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?

Four short sentences, zero filler, with the most decision-relevant fact (deferred cancellation) placed first and the safety warning last. Every sentence earns its place.

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 two-parameter destructive tool with full schema coverage and no output schema, the definition covers timing, side effects on the running VPS, and the confirmation gate. The only meaningful omission is reversibility — whether an agent's user can undo a pending cancellation.

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%, with both id (regex-constrained) and confirm already documented, so the baseline is 3. The description reinforces the confirm requirement ('You MUST set confirm to true') but adds no format or constraint detail beyond the schema.

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 ('Cancel a VPS subscription') and adds a crucial scope qualifier: cancellation takes effect at the end of the current billing period, not immediately. That deferred semantics implicitly distinguishes it from immediate-destruction siblings like vps_power or vps_reinstall_os, though no sibling is named 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?

The description makes the timing condition clear (end of billing period, VPS keeps running until expiry), which is implied guidance on when the tool takes effect. However, it never states when to prefer this over alternatives, nor whether the cancellation can be reversed before expiry, leaving the agent to infer the surrounding workflow.

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.