Skip to main content
Glama
Sign In

EQVPS — VPS and code sandboxes for AI agents

by io.github.Poiuyhje
OverviewDiscussionsAdmin

Delegate service access

delegate_service

Grant OPERATOR access to one of YOUR VPS to another person by email (they can power/reinstall/console/hostname/rdns, but NOT renew, cancel or change billing). Sends them an invitation with an accept link. Optional expires_days for time-limited access. Owner-only. Requires: token (owner).

Input Schema

NameRequiredDescriptionDefault
emailYesRequired. Email of the person who gets operator access, e.g. "admin@partner.org". They receive an invitation link.
service_idNoOptional. Service code as returned by list_vps/order_vps, e.g. "68J67T5" (a plain numeric id is also accepted).
expires_daysNoOptional. Access lifetime in days, integer 1–365. Default: no expiry (until revoked).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / email / description
      Added value: +"Required. Email of the person who gets operator access, e.g. \"admin@partner.org\". They receive an invitation link."
    • addedInput schema / properties / expires_days / description
      Added value: +"Optional. Access lifetime in days, integer 1–365. Default: no expiry (until revoked)."
    • 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",
-  "email"
-]New value: +[
+  "email"
+]
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), it discloses the actual permission envelope granted (power/reinstall/console/hostname/rdns but not renew/cancel/billing), that an invitation email with an accept link is sent, and that access is time-limited only if expires_days is supplied. This is the auth and effect-scope context an agent needs for a delegation 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?

The core action and its scope are front-loaded in the first clause, with the permission boundary immediately after. It is dense but nearly every clause earns its place, though 'Owner-only' and 'Requires: token (owner)' are mildly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-output-schema, 3-parameter mutation, the description covers the actor, effect, invitation flow, expiry, and auth requirement. The main omission is what the call returns (e.g. a delegation id) and what happens if the same email is delegated twice, which the non-idempotent annotation implies is possible.

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 email, service_id, and expires_days are already fully documented in the schema. The description restates expires_days as optional time-limited access but adds no syntax or constraint meaning beyond that, so the baseline 3 applies.

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 gives a precise verb (grant) and resource (OPERATOR access to one of YOUR VPS) plus the target (another person by email). It distinguishes itself cleanly from siblings like revoke_delegation, list_delegations, and accept_delegation, which handle the other stages of the same lifecycle.

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?

It states the prerequisite explicitly (owner-only, requires an owner token) and enumerates exactly what the delegatee may and may not do, which tells the agent when this tool is appropriate. It does not, however, route the agent to the counterpart tools (revoke_delegation to undo, list_delegations to audit), so the when-not side is only implicit.

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