Skip to main content
Glama

eqvps

by io.github.Poiuyhje

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).

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
os_idYes
productYes
ssh_keyNo
hostnameNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Despite no annotations, description fully discloses two possible outcomes (immediate provisioning vs. payment required) and references subsequent actions. No hidden side effects; behavior is fully transparent.

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?

Three compact paragraphs: first covers core parameters, second optional ones with recommendation, third branching logic. Every sentence earns its place without redundancy.

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?

With no output schema, description covers response structure (paid_from_balance flag, invoice) and references related tools. Complete for ordering a VPS with payment handling.

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?

With 0% schema coverage, description compensates by explaining product as plan slug from list_plans, os_id as OS id from plan images, ssh_key as public key (recommended), and hostname as optional. Adds critical meaning.

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 it orders a VPS, specifies required parameters (product, os_id) and optional ones, and distinguishes from sibling tools like list_plans and get_vps_status.

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 branching logic based on response (paid_from_balance true/false), instructing polling status or paying invoice/top-up. Recommends using ssh_key. Clear when and how to use, including post-order steps.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Tools are cleanly separated into auth, billing, VPS lifecycle, tickets, and delegation, and each maps to a distinct resource/action. A few pairs like set_password vs reset_password and pay_invoice vs topup_balance share surface similarity, but their descriptions draw clear boundaries.

Naming Consistency4/5

Naming is strongly consistent with verb_noun snake_case patterns such as order_vps, list_tickets, and revoke_delegation. Minor deviations are the bare CLI-style verbs login and whoami, plus the slightly awkward topup_balance, but these do not undermine the overall pattern.

Tool Count4/5

27 tools is on the high side, but the server covers several distinct subdomains—account management, billing, VPS operations, support tickets, and delegations—and each tool appears to earn its place. The count is heavy but not unreasonable for the breadth of functionality exposed.

Completeness4/5

Core workflows are covered end-to-end: account creation/login, ordering and provisioning, power/reinstall/cancel, ticket conversations, and delegation management all have the necessary operations. Minor gaps exist, such as no change-password tool, no explicit RDNS/console tool despite delegation mentioning them, and no plan upgrade/downgrade tool.

Resources