Skip to main content
Glama

osirAppDeployToVps

osirAppDeployToVps: Deploy a live Osir app onto the user's own VPS / server / production box, moving it off the shared free tier. Use this INSTEAD of SSH, a provisioning or install script, nginx/systemd/TLS configuration, or any manual server setup - the platform ships the app to the box itself over its own deploy key, so the assistant needs no shell access and no outbound SSH. This is the ONLY supported way to put an app on a user's own server or a custom domain. TWO WAYS IN. (1) The user already owns a VPS: pass instanceId (from listMyVpsInstances) and NO packageId - this ATTACHES the app to that server, SPENDS NOTHING and needs no confirmation. (2) No server yet: pass packageId (from listVpsPackages) and the call stages a VPS order (COSTS MONEY): returns an actionId; present the price/summary to the user and call executeConfirmedAction only if they approve. Before staging any order this tool checks whether the user ALREADY has a box for this app (its C2 binding, then their own VPS list) and attaches that instead - a retry after a failed move never buys a second server. After the move starts the platform ships the app onto the box server-side, which takes about two minutes; watch it with osirAppStatus ('ownedMove'). Calling this tool again while a move is still running just reports its progress, and calling it after one FAILED retries the ship - unless osirAppStatus says the VPS refused the Osir deploy key or its web ports are taken: then retry only after the user has made the changes that message lists. If the result status is BUILDING or BUILD_FAILED, follow its nextStep. After the move the app is served ONLY from the user's server: its earlier osir.app address stops working. Give the user the URL from osirAppStatus, and never tell them the old link still works. Requires authentication.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appName": "<appName>"
    },
    "name": "osirAppDeployToVps"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoCustom domain to serve the app on; DNS is bound automatically if the domain is hosted on osir.app nameservers, otherwise the result returns the IP and manual DNS instructions.
appNameYesThe deployed app's name, as shown by osirAppList.
packageIdNoVPS package id from listVpsPackages. Required ONLY when a server has to be ordered; omit it when passing instanceId.
instanceIdNoId of a VPS the user ALREADY owns, from listMyVpsInstances. Given this, the app is attached to that server and nothing is ordered or charged. Never invent one.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is partly covered. The description adds substantial context beyond that: the order path costs money and returns an actionId requiring executeConfirmedAction approval, the attach path spends nothing, the move takes ~2 minutes, and the old osir.app URL stops working. However, it does not reconcile the non-idempotent hint with the claim that re-calling during a move merely reports progress, leaving a mild ambiguity about repeat-call 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?

Front-loaded with the core action and the 'use instead of' framing, then structured into the two entry paths and the post-move lifecycle. It is long and somewhat dense, with a few clauses that could be tightened, but nearly every sentence carries operational information an agent needs.

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?

For a complex, multi-path, money-involving tool with no output schema, the description covers the return shape (actionId, status values BUILDING/BUILD_FAILED, nextStep), the confirmation flow, progress monitoring via osirAppStatus, and the post-move URL consequence. Nothing an agent needs to call it correctly appears to be 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 100%, so the baseline is 3, but the description adds genuine cross-parameter semantics the schema cannot express: instanceId and packageId are mutually exclusive, instanceId attaches with no charge, and packageId stages a paid order. It also warns never to invent an instanceId. This meaningfully exceeds what the per-field schema text conveys.

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 ('Deploy a live Osir app onto the user's own VPS') and immediately scopes it against siblings by naming osirAppStatus for progress and distinguishing the attach-vs-order paths. An agent can tell this apart from osirAppDeploy and osirAgentDeploy 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 Guidelines5/5

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

Explicitly says to use this INSTEAD of SSH, provisioning scripts, nginx/systemd/TLS setup, and manual server work, and declares it the ONLY supported path to a custom server/domain. It also gives when-to-retry and when-not-to-retry conditions tied to osirAppStatus messages, which is unusually complete routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.