Skip to main content
Glama

OSIR Domain Registrar

by com.osir
OverviewDiscussionsAdmin

orderVps

orderVps: Stage an order for a new VPS instance; deducts from account balance. If this server is being ordered to host an Osir app, do NOT configure it by hand afterwards: deploy the app with osirAppDeploy, then put it on the box with osirAppDeployToVps. Requires authentication. Returns an actionId: present the summary to the user, then call executeConfirmedAction with the actionId if they approve.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostnameYesHostname for the new server, e.g. 'myserver.example.com'.
packageIdYesVPS package id from listVpsPackages.
sshKeyIdsNoInteger SSH key ids from listMySshKeys or addSshKey, injected during install; without one you cannot log in.
sessionKeyNoSession key (osk_...) returned by checkDeviceLoginStatus. Pass it on every call when logged in via the in-chat device flow; omit when connected via OAuth.
paymentTermYesBilling cycle: 'MONTHLY', 'SEMI_ANNUAL', 'ANNUAL', 'BIENNIAL', or 'TRIENNIAL'.
operatingSystemIdNoInteger OS template id resolved with listVpsOsTemplates using this same packageId; omit to get a server with NO operating system installed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / hostname / description
      Added value: +"Hostname for the new server, e.g. 'myserver.example.com'."
    • addedInput schema / properties / operatingSystemId / description
      Added value: +"Integer OS template id resolved with listVpsOsTemplates using this same packageId; omit to get a server with NO operating system installed."
    • addedInput schema / properties / packageId / description
      Added value: +"VPS package id from listVpsPackages."
    • addedInput schema / properties / paymentTerm / description
      Added value: +"Billing cycle: 'MONTHLY', 'SEMI_ANNUAL', 'ANNUAL', 'BIENNIAL', or 'TRIENNIAL'."
    • addedInput schema / properties / sshKeyIds / description
      Added value: +"Integer SSH key ids from listMySshKeys or addSshKey, injected during install; without one you cannot log in."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare non-readonly/non-idempotent/non-destructive). It discloses that the order deducts from the account balance, requires authentication, returns an actionId, and must be confirmed via executeConfirmedAction — the exact two-step staging behavior an agent needs.

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?

Purpose and the balance impact are front-loaded, followed by the Osir routing and the confirmation flow. Efficient overall, with only minor waste in the leading 'orderVps:' restating the tool name.

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, yet the description still explains the return (actionId) and the required follow-up flow. For a mutating, money-affecting order tool, the auth, cost, and confirmation details are all present.

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 coverage is 100% and every parameter is described in the schema (packageId source, sshKeyIds, paymentTerm enum, OS template, sessionKey). The description adds no parameter-level syntax or format detail, so baseline 3 is appropriate.

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 ('stage an order for a new VPS instance') and adds scope ('deducts from account balance'). An agent can distinguish it from siblings like buildVpsInstance or listVpsPackages without opening the 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?

Gives explicit conditional routing: if the box is for an Osir app, do NOT configure by hand — deploy with osirAppDeploy then osirAppDeployToVps. It also names the follow-up tool executeConfirmedAction and the approval condition that selects it, leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OSIR Domain Registrar 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