Skip to main content
Glama

eqvps

by io.github.Poiuyhje
OverviewDiscussionsAdmin

Get VPS status & access

get_vps_status

Get full detail for one VPS: status, specs, live VM state/uptime, and access info (host, port, ready-to-paste command; access.method = ssh for Linux, rdp for Windows — port follows the plan: dedicated IP 22/3389, NAT 20000+vmid). ROOT PASSWORD (keyless VPS): call with reveal: true to retrieve it. It is shown ONCE, and only after the VM has finished booting — at that moment the password is applied to the live VM, so it is guaranteed to work. While the VM is still booting the response carries password_pending: true and NO password; just call again with reveal: true in ~30-60s (the one-time reveal is NOT spent until a password is actually returned — no reset or reboot needed). Without reveal, password_available: true means a password is waiting to be revealed. If you supplied an SSH key at order time, log in with that key (no password); ssh_ready: false means the VM is still booting — retry shortly. Use reset_password ONLY if the password is lost. Poll this (without reveal) after order_vps to watch provisioning reach active. NAT plans (no dedicated IP): the SSH port shown is an EXTERNAL DNAT port forwarded to the VM internal port 22 (internal_port in the response). If you configure a host firewall, allow the INTERNAL port — ufw allow OpenSSH — NOT the external port, or ufw enable will lock SSH out. See firewall_note in the response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
revealNo
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"
    • removedInput schema / required
      Removed value: -[
-  "service_id"
-]
  2. Changed1 schema field changed
    • addedInput schema / properties / reveal
      Added value: +{
+  "type": "boolean"
+}
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: password shown once, password_pending flag, one-time reveal not spent until password returned, ssh_ready meaning, and NAT port forwarding. It explains side effects and prerequisites in depth.

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?

Long but every sentence carries load-bearing detail; no filler. Starts with core purpose, then flows into access info, password reveal, boot behavior, polling, NAT specifics, and firewall caution—logical progression that front-loads the most critical usage.

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?

The tool is complex (status, provisioning, password reveal, NAT port forwarding, firewall interplay) and has no output schema. The description covers boot timing, password lifecycle, SSH key login, NAT DNAT port mapping, and internal vs external firewall ports, leaving little for an agent to infer.

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?

Despite schema coverage at 50%, the description adds rich semantics: reveal is explained (true retrieves password, absent returns password_available), and service_id is tied to list_vps/order_vps with an example. It compensates for the missing reveal schema description and clarifies default behavior.

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 opens with a specific verb and resource: 'Get full detail for one VPS' and enumerates the exact content (status, specs, live VM state/uptime, access info). It immediately distinguishes from siblings by naming what it is not (e.g., list_vps, reset_password) and by covering the one-time password reveal, which is unique to this tool.

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?

Provides explicit when-to-use instructions: polling after order_vps, retrying during boot, and using reset_password only if the password is lost. It also covers the NAT firewall scenario and SSH key login, which clarify when alternative actions are needed.

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