Skip to main content
Glama
Sign In

EQVPS — VPS and code sandboxes for AI agents

by io.github.Poiuyhje
OverviewDiscussionsAdmin

Set hostname

set_hostname
Idempotent

Set the VPS hostname (valid DNS name). Applied immediately inside the running server via the guest agent (Linux: hostnamectl + the 127.0.1.1 line in /etc/hosts; Windows: renamed, takes effect after a reboot — the response then has reboot_required: true). The server must be running with its guest agent active; otherwise the call fails with 409 agent_unavailable and nothing is changed. Your password, SSH host keys and files are not touched. Requires: token, server running. Typical error: 409 agent_unavailable → start the server / wait for boot.

Input Schema

NameRequiredDescriptionDefault
hostnameYesRequired. New hostname, a valid DNS name up to 128 characters (letters, digits, dots, hyphens; no leading/trailing dot or hyphen), e.g. "db-2.example.org".
service_idNoOptional. Service 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. Changed2 schema fields changed
    • addedInput schema / properties / hostname / description
      Added value: +"Required. New hostname, a valid DNS name up to 128 characters (letters, digits, dots, hyphens; no leading/trailing dot or hyphen), e.g. \"db-2.example.org\"."
    • changedInput schema / properties / service_id / description
      Previous value: -"Service code as returned by list_vps/order_vps, e.g. \"68J67T5\" (a plain numeric id is also accepted)."New value: +"Optional. Service code as returned by list_vps/order_vps, e.g. \"68J67T5\" (a plain numeric id is also accepted)."
  2. 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",
-  "hostname"
-]New value: +[
+  "hostname"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Far exceeds the annotations: it discloses the guest-agent mechanism, immediate application on Linux vs reboot-required on Windows, the 409 agent_unavailable atomic-failure guarantee, and reassures that password/SSH keys/files are untouched. This is exactly the behavioral context an agent needs before a mutation.

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?

One dense paragraph front-loaded with the action, then mechanism, preconditions, safety and error. Every clause earns its place, though the stacked parentheticals make it slightly heavy to scan.

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, the description still surfaces the key response field (reboot_required: true) and covers prerequisites, failure modes and non-destructive scope. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the hostname parameter already documents the DNS-name format, length limit and an example, so the description adds little parameter meaning. Baseline 3 applies when the schema does the heavy lifting.

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 and resource (set the VPS hostname) and immediately qualifies it with the expected format (valid DNS name). An agent can distinguish it from siblings like reset_password or reinstall_vps without opening a schema.

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 explicit preconditions (server running, guest agent active) and a remediation path for the typical failure (409 agent_unavailable → start the server / wait for boot). It does not need to name an alternative since no sibling performs this operation, which keeps it short of a 5 but genuinely helpful.

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