Skip to main content
Glama
Sign In

EQVPS — VPS and code sandboxes for AI agents

by io.github.Poiuyhje
OverviewDiscussionsAdmin

Register a new account

register_account

Create a NEW EQVPS customer account (first_name, last_name, email). Use a real email address you control — reserved/test domains such as example.com are not suitable (no recovery, no notifications). Returns a bearer token that is reusable for every request until token_expires_at (1 year by default; optional token_ttl_days 1-1825) — it is NOT single-use; call refresh_token before it expires. Inside this MCP session the token is remembered automatically for the following tool calls. If you call the server with raw HTTP/curl instead, save the token to a file right away and send Authorization: Bearer <token> on EVERY request — a shell variable does not survive separate commands. Never call register_account again to "get a new token": that creates another, empty account. Optional backup: call set_password once, then login (email + password) returns a fresh token if this one is lost. Requires: nothing. Typical error: 422 email already registered → use login or your saved token instead of a new account.

Input Schema

NameRequiredDescriptionDefault
emailYesRequired. Real email address you control (login, recovery and service emails), e.g. "ops@yourcompany.com". Reserved/test domains such as example.com are rejected in practice.
last_nameYesRequired. Account holder's last name, 1+ characters, e.g. "Smith".
first_nameYesRequired. Account holder's first name, 1+ characters, e.g. "Alex".
token_ttl_daysNoOptional. Token lifetime in days (default 365).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / email / description
      Added value: +"Required. Real email address you control (login, recovery and service emails), e.g. \"ops@yourcompany.com\". Reserved/test domains such as example.com are rejected in practice."
    • addedInput schema / properties / first_name / description
      Added value: +"Required. Account holder's first name, 1+ characters, e.g. \"Alex\"."
    • addedInput schema / properties / last_name / description
      Added value: +"Required. Account holder's last name, 1+ characters, e.g. \"Smith\"."
    • changedInput schema / properties / token_ttl_days / description
      Previous value: -"Token lifetime in days (default 365)."New value: +"Optional. Token lifetime in days (default 365)."
  2. Changed1 schema field changed
    • addedInput schema / properties / token_ttl_days
      Added value: +{
+  "description": "Token lifetime in days (default 365).",
+  "maximum": 1825,
+  "minimum": 1,
+  "type": "integer"
+}
  3. Changed2 schema fields changed
    • removedInput schema / properties / password
      Removed value: -{
-  "minLength": 8,
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "first_name",
-  "last_name",
-  "email",
-  "password"
-]New value: +[
+  "first_name",
+  "last_name",
+  "email"
+]
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare the safety profile (not read-only, not destructive, not idempotent), and the description adds substantial non-obvious context: token is reusable and single-use=false, 1-year default lifetime, auto-remembered inside the MCP session, must be persisted manually over raw HTTP/curl, and the 422 already-registered behavior.

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?

Dense and front-loaded: the core action and the token's reusability lead, with operational caveats after. It is long, but nearly every clause carries an actionable instruction; the only mild redundancy is the email advice and the repeated 'don't register again' warning, which overlaps the 422 note.

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?

No output schema exists, so the description carries the return burden and does so fully, explaining the bearer token, its lifetime, the token_ttl_days control, and the refresh path. For a mutation tool with side effects (empty account on repeat), nothing an agent needs to call 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%, so the schema already documents all four parameters including the email constraint and token_ttl_days range. The description largely restates the email advice ('no recovery, no notifications') and the TTL bound already present in the schema, adding rationale but little new syntax.

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?

Opens with a specific verb+resource: 'Create a NEW EQVPS customer account', naming the required fields. It also distinguishes itself from siblings (login, set_password, refresh_token) by explaining that re-calling it creates an empty account, so an agent can route correctly 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when-not-to-use it (never re-register for a new token; use login if the email is already registered), names alternatives (refresh_token before expiry; set_password + login as backup), and gives the precondition 'Requires: nothing'. The 422 branch is documented with the corrective action.

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