Skip to main content
Glama

EQVPS — VPS and code sandboxes for AI agents

by io.github.Poiuyhje
OverviewDiscussionsAdmin

Order a VPS

order_vps

Order a VPS. product = plan slug from list_plans; os_id = an OS id from that plan's images. Optional hostname and ssh_key (public key — strongly recommended so you get key-based root login). Optional location: "de" (Germany) or "fi" (Finland) — omit it and we pick the location automatically; if the chosen country has no free capacity for that plan the call fails with 409 location_unavailable (nothing is charged) and available lists the countries that can take it. Optional period ("month" by default, or "year" for annual billing) or an explicit plan_id from list_plans plans[]; an active automatic offer (plans[].promo) is applied to the first invoice and the response then carries promo. Windows plans (windows-*) accept only the Windows Server 2022 image, ignore ssh_key, and are reached over RDP as Administrator (see get_vps_status → access); the licence is BYOL.

Branching on the response: • paid_from_balance: true → the prepaid balance covered it; the server is provisioning. Poll get_vps_status until status is active and the VM is reachable. • paid_from_balance: false → balance was insufficient; an unpaid invoice is returned. Call pay_invoice with invoice.id to get a crypto checkout_url, OR topup_balance then re-order. PROMO until 2026-10-31 23:59 Europe/Kyiv: -25% on ANNUAL billing, first year only, applied automatically (no code) to windows-medium ($171/yr), windows-small-ip ($252/yr) and windows-medium-ip ($324/yr); renewal at the regular annual price; windows-small not included — order with period="year". Requires: token + enough balance (else an unpaid invoice is returned). Typical errors: 409 location_unavailable (see available), 422 unknown product/os_id (see list_plans).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
os_idYes
periodNo
plan_idNo
productYes
ssh_keyNo
hostnameNo
locationNoOptional server country: "de" (Germany) or "fi" (Finland). Omit for automatic placement.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / location
      Added value: +{
+  "description": "Optional server country: \"de\" (Germany) or \"fi\" (Finland). Omit for automatic placement.",
+  "enum": [
+    "de",
+    "fi"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / period
      Added value: +{
+  "enum": [
+    "month",
+    "year"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / plan_id
      Added value: +{
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: it discloses the balance-vs-invoice behavior, the 409 location_unavailable outcome (nothing charged, `available` populated), 422 semantics, the Windows-plan quirks (fixed image, ignored ssh_key, RDP/BYOL), and the automatic promo application. These are non-obvious behavioral traits an agent could not infer from the schema.

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 core action and logically segmented with parameter notes and a bulleted response branch. It is long, though, and the PROMO block is verbose promotional detail that reads as tangential to correct invocation, slightly diluting the otherwise tight structure.

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?

There is no output schema, so the description must explain returns, and it does: paid_from_balance, invoice.id, checkout_url, promo, and the resulting status flow. Combined with error handling and prerequisites, an agent has everything needed to call and follow up correctly.

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 description coverage is only 14%, so the description must compensate, and it does: it defines product (plan slug from list_plans), os_id (image id for that plan), ssh_key (public key, key-based root login), location (de/fi, auto-placement if omitted), period (default month vs year), and plan_id. Every parameter gains meaning beyond the bare schema types.

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?

Opens with a specific verb+resource ('Order a VPS') and immediately differentiates itself from siblings by pointing at list_plans, get_vps_status, pay_invoice, and topup_balance for the related steps. An agent can tell this is the provisioning entry point versus the status/payment tools without opening any 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?

Explicitly covers when to use it and what to do next via response branching (paid_from_balance true → poll get_vps_status; false → pay_invoice OR topup_balance then re-order). It even names the prerequisite (token + balance) and the fallback path when balance is insufficient.

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