Skip to main content
Glama

EQVPS — VPS and code sandboxes for AI agents

by io.github.Poiuyhje
OverviewDiscussionsAdmin

Set hostname

set_hostname

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

TableJSON Schema
NameRequiredDescriptionDefault
hostnameYes
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",
-  "hostname"
-]New value: +[
+  "hostname"
+]
  2. First observed

TDQS

A4.6/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: it explains the mechanism (guest agent; hostnamectl + 127.0.1.1 line on Linux; rename on Windows), the delayed Windows effect with the `reboot_required: true` response field, the atomic failure mode (409 changes nothing), and an explicit non-impact list (password, SSH host keys, files untouched). This is exactly the behavioral context an agent needs before mutating a host.

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?

Information-dense and reasonably front-loaded, leading with the action and format before mechanism and failure modes. The parenthetical platform detail is long but each clause carries distinct operational meaning, so little is wasted.

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?

There is no output schema, yet the description still discloses the one return field that matters (`reboot_required: true` on Windows) and covers prerequisites, failure codes, and side-effect boundaries. Nothing material an agent needs to call this correctly is missing.

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 50%; the undocumented parameter is the required `hostname`, and the description compensates by stating it must be 'a valid DNS name'. The other parameter (service_id) is already documented in the schema, so the description adds the one piece of semantics the schema omits.

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 ('Set the VPS hostname') and immediately qualifies the required format ('valid DNS name'). No sibling tool touches hostnames, so the purpose is unambiguous without opening any 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 prerequisites ('server must be running with its guest agent active', 'Requires: token, server running') and the failure condition plus remediation (409 agent_unavailable → start the server / wait for boot). It never names an alternative tool, but none exists for this operation, so the gap is minor.

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