Skip to main content
Glama

OSIR Domain Registrar

by com.osir
OverviewDiscussionsAdmin

osirAppDeploy

osirAppDeploy: Deploy an app to Osir (free tier) and get a live HTTPS URL; the app runs isolated in a microVM. Deploying an existing app name redeploys it (new version) and applies any secrets set via osirAppSetSecret. A plain static website (HTML/CSS/JS with no framework or build step) is also supported: it is auto-detected and served directly; pass language 'node' for it. To put the app on the user's OWN VPS, server or production box instead, deploy it here first and then call osirAppDeployToVps - never SSH into the box or write an install script. Once an app is on the user's own VPS, redeploying HERE under the same name is how you update it: the platform re-ships it to the box and keeps its domain. Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesApp name: lowercase letters, digits, and hyphens, e.g. 'habit-tracker'.
regionNoRegion: 'us' or 'al' ('al' is Albania/Tirana); defaults to the platform's home region.
languageYesRuntime language: 'node', 'python', 'php-laravel', or 'go'; use 'node' for a plain static site.
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.
uploadTicketYesUpload ticket from osirAppCreateUpload, after uploading the zipped source to its putUrl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / language / description
      Added value: +"Runtime language: 'node', 'python', 'php-laravel', or 'go'; use 'node' for a plain static site."
    • addedInput schema / properties / name / description
      Added value: +"App name: lowercase letters, digits, and hyphens, e.g. 'habit-tracker'."
    • addedInput schema / properties / region / description
      Added value: +"Region: 'us' or 'al' ('al' is Albania/Tirana); defaults to the platform's home region."
    • addedInput schema / properties / uploadTicket / description
      Added value: +"Upload ticket from osirAppCreateUpload, after uploading the zipped source to its putUrl."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent), and the description adds substantial behavior beyond them: redeploy-under-same-name creates a new version and applies secrets set via osirAppSetSecret, static sites are auto-detected and served directly, and authentication is required. It also warns against the wrong operational path (SSH/install scripts).

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 but front-loaded: the core action and outcome come first, then redeploy semantics, then static-site handling, then the VPS workflow. A few clauses (e.g., the emphatic 'never SSH into the box') are repetitive within the same sentence, costing a little tightness.

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 5-parameter mutation tool with no output schema, the description covers the return value (live HTTPS URL), auth requirement, redeploy/update semantics, secret application, and the VPS handoff workflow. 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 name, region, language, sessionKey, and uploadTicket including the 'node for static' rule. The description repeats the language guidance but adds no new syntax or format meaning for any parameter, 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?

States a specific verb and resource ('Deploy an app to Osir') plus the observable outcome (a live HTTPS URL) and the runtime model (isolated microVM). It also explicitly distinguishes itself from its closest sibling, osirAppDeployToVps, so an agent can route correctly without opening either 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 when-to-use rules: use this first for the user's own VPS and then call osirAppDeployToVps; never SSH or write install scripts; redeploying here under the same name is the update path for VPS-hosted apps. This is a full routing policy, not just context.

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