Skip to main content
Glama
Sign In

EQVPS — VPS and code sandboxes for AI agents

by io.github.Poiuyhje
OverviewDiscussionsAdmin

Cancel a VPS

cancel_service
Destructive

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

NameRequiredDescriptionDefault
typeNoOptional. "end_of_period" (default: runs until the paid period ends, undoable) or "immediate" (destroys the server and all data now).
reasonYesRequired. Why this VPS is being cancelled (e.g. project finished, too expensive, no longer needed).
confirmNoOptional. Needed only with type "immediate": the server's exact hostname (from get_vps_status). Ask the human first.
service_idNoOptional. Service 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. Changed4 schema fields changed
    • addedInput schema / properties / confirm / description
      Added value: +"Optional. Needed only with type \"immediate\": the server's exact hostname (from get_vps_status). Ask the human first."
    • changedInput schema / properties / reason / description
      Previous value: -"REQUIRED: why this VPS is being cancelled (e.g. project finished, too expensive, no longer needed)."New value: +"Required. Why this VPS is being cancelled (e.g. project finished, too expensive, no longer needed)."
    • changedInput schema / properties / service_id / description
      Previous value: -"Service code as returned by list_vps/order_vps, e.g. \"68J67T5\" (a plain numeric id is also accepted)."New value: +"Optional. Service code as returned by list_vps/order_vps, e.g. \"68J67T5\" (a plain numeric id is also accepted)."
    • addedInput schema / properties / type / description
      Added value: +"Optional. \"end_of_period\" (default: runs until the paid period ends, undoable) or \"immediate\" (destroys the server and all data now)."
  2. 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"
+]
  3. 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"
+]
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, but the description goes well beyond them: it explains that immediate permanently destroys the VM and all data, that end_of_period causes no data loss now, that immediate requires confirm=hostname, and that unused paid time is refunded. It omits only details like whether the refund is automatic vs. queued and any latency before destruction takes effect.

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?

Safety-critical information is front-loaded and every sentence carries real instruction. It is dense with parentheticals and back-references ('refund as above', 'see refund_amount'), which slows scanning slightly for an otherwise high-value block of text.

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 destructive, irreversible operation with no output schema, the description supplies prerequisites (token + reason, plus confirm for immediate), the refund behavior and where to read it in the response, the state check via get_vps_status, and the recovery paths. Nothing material is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds relational meaning the schema cannot: that confirm is only meaningful together with type=immediate, that its value must be the exact server hostname sourced from get_vps_status, and that the response carries refund_amount. This is genuine value beyond the field-level descriptions.

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 (cancel) on a specific resource (a VPS) and immediately distinguishes the two modes, end_of_period vs immediate. It also names sibling tools it interacts with (get_vps_status, undo_cancel), so an agent can tell it apart from those directly.

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?

Gives an explicit default recommendation ('Use end_of_period unless you explicitly intend to wipe the server now'), names the alternative tool for reversing a scheduled cancellation (undo_cancel), and even prescribes the handling for the typical 409 cancellation_already_scheduled response.

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