Skip to main content
Glama

eqvps

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.

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.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It clearly discloses the destructive nature (all data lost) and the mandatory confirmation step, plus async execution. It doesn't detail other side effects like downtime, but the critical safety information is present.

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?

Two sentences, no fluff. The destructive warning is front-loaded, and each sentence adds necessary guidance. Very efficient.

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 reinstall operation, the description covers the required confirmation, the parameters, and the asynchronous behavior with polling instruction. With no output schema, it doesn't specify return values, but it tells the agent what to do next. Complete enough.

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 covers only service_id with a description (33%). The description adds crucial semantics for os_id (from list_plans) and confirm (exact hostname or 'DELETE'), effectively compensating for the missing schema descriptions on those parameters.

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?

The description clearly states the tool's purpose: wipes and reinstalls the VPS with a given OS image. It references related tools (list_plans for os_id, get_vps_status for hostname) and distinguishes itself from other VPS management tools by its destructive nature.

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 instructs that the agent must confirm with the human, requires confirm to be exact hostname or 'DELETE', and explains async provisioning with polling guidance. This gives clear when-to-use and how-to-use instructions.

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

All eqvps 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