Skip to main content
Glama

EQVPS — VPS and code sandboxes for AI agents

by io.github.Poiuyhje
OverviewDiscussionsAdmin

Cancel a VPS

cancel_service

Cancel a VPS. DEFAULT end_of_period: the server stays active until the end of the already-paid period, then is simply not renewed — NO data loss now, safe. immediate DESTROYS the VM and ALL data right away, permanently and irreversibly, and REQUIRES confirm set to the exact server hostname (see get_vps_status). Use end_of_period unless you explicitly intend to wipe the server now. On immediate, the unused portion of the already-paid period is refunded to your account balance (see refund_amount in the response). Already scheduled end_of_period? Call undo_cancel to keep the server, or call cancel_service again with type=immediate + confirm to switch to immediate destruction (refund as above). get_vps_status shows cancellation {type, cancel_at, can_undo}. Requires: token + reason; immediate also needs confirm=hostname. Typical: 409 cancellation_already_scheduled → undo_cancel, or repeat with type=immediate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
reasonYesREQUIRED: why this VPS is being cancelled (e.g. project finished, too expensive, no longer needed).
confirmNo
service_idNoService code as returned by list_vps/order_vps, e.g. "68J67T5" (a plain numeric id is also accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / service_id / description
      Added value: +"Service code as returned by list_vps/order_vps, e.g. \"68J67T5\" (a plain numeric id is also accepted)."
    • removedInput schema / properties / service_id / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / service_id / minLength
      Added value: +1
    • changedInput schema / properties / service_id / type
      Previous value: -"integer"New value: +"string"
    • changedInput schema / required
      Previous value: -[
-  "service_id",
-  "reason"
-]New value: +[
+  "reason"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "REQUIRED: why this VPS is being cancelled (e.g. project finished, too expensive, no longer needed).",
+  "maxLength": 500,
+  "minLength": 3,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "service_id"
-]New value: +[
+  "service_id",
+  "reason"
+]
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does: it discloses that immediate permanently and irreversibly destroys VM and data, that end_of_period causes no data loss now, that refunds flow to account balance, and that auth (token) plus confirm=hostname are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the default behavior and reasonably dense, with every sentence carrying operational value. It is slightly run-on and emphasis-heavy, but there is little genuine waste.

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?

Despite no output schema, it explains the relevant response fields (refund_amount, cancellation {type, cancel_at, can_undo}) and full prerequisite/error handling. An agent has everything needed to call it correctly and recover from the common failure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the description more than compensates: it explains the meaning/danger of each `type` enum value and clarifies that `confirm` must equal the exact server hostname. This adds meaning well beyond the bare enum and undocumented `confirm` field.

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?

States a specific verb+resource ('Cancel a VPS') and immediately differentiates its two operating modes. It names siblings (undo_cancel, get_vps_status) so an agent can distinguish it from adjacent tools without opening schemas.

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?

Explicitly says 'Use end_of_period unless you explicitly intend to wipe the server now', and covers the already-scheduled case with the exact remediation path (undo_cancel, or re-call with type=immediate + confirm). The 409 cancellation_already_scheduled error path is spelled out with the alternative to take.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EQVPS — VPS and code sandboxes for AI agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources