Skip to main content
Glama

EQVPS — VPS and code sandboxes for AI agents

by io.github.Poiuyhje
OverviewDiscussionsAdmin

Reinstall OS

reinstall_vps

DESTRUCTIVE — all data is lost. REQUIRES confirm = exact hostname (from get_vps_status) or 'DELETE'. Agent must explicitly confirm with the human before calling. Wipes and reinstalls the VPS with the given OS image (os_id from list_plans). Provisioning runs asynchronously; poll get_vps_status. Requires: token + confirm (hostname or DELETE). Destroys all data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
os_idYes
confirmYes
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",
-  "os_id",
-  "confirm"
-]New value: +[
+  "os_id",
+  "confirm"
+]
  2. First observed

TDQS

A4.4/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 delivers: irreversible data loss, mandatory human confirmation, the confirm-token protocol, required auth (token), and asynchronous provisioning with a polling instruction. This is exactly the behavioral context an agent needs before invoking a destructive tool.

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

Conciseness3/5

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

The critical warning is correctly front-loaded, but the description is repetitive: 'all data is lost' and 'Destroys all data' bookend the text, and confirm/token requirements are stated twice. Trimming the duplication would tighten it without losing information.

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 destructive, async, no-output-schema tool with zero annotations, the description covers safety, prerequisites, input sourcing, and the polling follow-up. It could note what the async kickoff returns (e.g., a task id for get_vps_status), but overall it is complete enough to call correctly.

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 only 33% (only service_id is described in-schema), so the description must compensate. It explains os_id's source (list_plans) and confirm's accepted values (exact hostname from get_vps_status or 'DELETE'), covering both undocumented required params meaningfully.

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 and outcome: 'Wipes and reinstalls the VPS with the given OS image.' It also distinguishes scope (full OS reinstall vs. other service operations) clearly enough that an agent won't confuse it with change_plan or power_vps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives strong precondition guidance: confirm must be the exact hostname or 'DELETE' and the agent must explicitly confirm with the human before calling. It also routes input sourcing (os_id from list_plans, hostname from get_vps_status). It does not name alternative tools for non-destructive paths, so it stops short of a 5.

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