Skip to main content
Glama

osirAppStatus

Read-onlyIdempotent

osirAppStatus: Get an Osir app's current status, live URL, and health ('is my app working?'). If the status is BUILD_FAILED, 'recentErrors' explains why so you can fix the source and redeploy. 'qa' is an independent black-box check of the LIVE app after deploy: qa.status PASSED means it loaded and worked; FAILED means it deployed but didn't actually work, and qa.findings lists the problems so you can fix and redeploy. 'ownedMove' tracks a move onto the user's own VPS, which leaves tier and status unchanged while it runs: state MOVING (in progress, stage says where, ~2 minutes in total), MOVED (done - tier reads 'owned'), FAILED or REFUSED (follow this result's message: usually call osirAppDeployToVps again to retry, which never orders a second server; but when the VPS refused the Osir deploy key or its web ports are taken, the user must fix the VPS first, and the message says how). For an app on the user's own VPS (tier 'owned'), health is always UNKNOWN: the platform does not probe the user's server. Use qa to tell whether it works; do not redeploy because of UNKNOWN. 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": {
      "appId": "<appId>"
    },
    "name": "osirAppStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesApp id from osirAppList or a deploy result.
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. Changed1 schema field changed
    • addedInput schema / properties / appId / description
      Added value: +"App id from osirAppList or a deploy result."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent read, and the description goes well beyond them: it explains that health is always UNKNOWN for owned-tier apps so the agent doesn't misinterpret it, that ownedMove leaves tier and status unchanged while running, and that the tool requires authentication. Strong added context, though it doesn't discuss response shape or latency beyond the ~2 minute move estimate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and every sentence carries information, but it's a dense run-on with deeply nested parentheticals around ownedMove that taxes readability. It could be restructured into clearly separated status/qa/ownedMove cases to reduce cognitive load.

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?

With no output schema, the description takes on documenting return fields, and it covers status, live URL, health, recentErrors, qa.status/findings, ownedMove.state/stage, and tier. That's substantial for this complexity, though the full set of returned fields is not enumerated.

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% and both parameters are self-documented, so this dimension should sit near baseline; the description matches rather than adds to them. It goes slightly past the baseline by noting that appId comes from osirAppList or a deploy result and by adding authentication context that reinforces the sessionKey requirement.

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 plus the concrete fields returned: "Get an Osir app's current status, live URL, and health", and frames it as the 'is my app working?' question. An agent can immediately distinguish it from deploy, list, logs, and delete siblings.

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?

Gives actionable when-to-use guidance for each outcome (BUILD_FAILED -> read recentErrors, qa FAILED -> fix and redeploy, ownedMove FAILED/REFUSED -> call osirAppDeployToVps again) and an explicit when-not: "do not redeploy because of UNKNOWN". It stops short of a direct statement about when to call this versus osirAppList or osirAppLogs, so it falls one step short of a 5.

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.