Skip to main content
Glama

osirAppGetSource

Read-onlyIdempotent

osirAppGetSource: Get a deployed Osir app's current source, to make edits without the user re-attaching the project. With inline=true it returns the files themselves: patch them and call osirAppDeploy with ALL the files under the SAME name; the platform rebuilds and, for owned-tier apps, auto-ships the new version to the user's box. If the result says truncated=true the files are only PART of the app - do NOT redeploy from them. Without inline it returns only a short-lived signed zip URL (getUrl), useful only to a client with a shell. 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": "osirAppGetSource"
  }
}

Input Schema

NameRequiredDescriptionDefault
inlineNotrue (recommended): return the files themselves (up to 300 files / 2 MiB). false/omitted: only a signed zip URL.
appNameYesThe deployed app's name, as shown by osirAppList.
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 / inline
      Added value: +{
      +  "description": "true (recommended): return the files themselves (up to 300 files / 2 MiB). false/omitted: only a signed zip URL.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / appName / description
      Added value: +"The deployed app's name, as shown by osirAppList."
  3. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description nonetheless adds real behavioral context beyond them: the signed URL is short-lived, results can be truncated (300 files / 2 MiB), owned-tier apps auto-ship on redeploy, and authentication is required with sessionKey passed on every device-flow call.

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 purpose, then the inline branch, then the truncation warning and auth note. Dense and largely waste-free, though the long multi-clause sentences (especially the deploy instruction) could be split for faster scanning.

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 exists, yet the description covers the return shape (files vs getUrl, truncated flag) and the limits that determine whether the result is usable. Auth and session handling are also addressed, so an agent has everything needed to call it correctly.

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 meaning the schema does not: the practical consequence of inline=true vs the URL-only mode, the truncation risk attached to inline results, and the 'SAME name' constraint that governs how appName must be reused on redeploy.

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 ('Get a deployed Osir app's current source') plus the motivation ('make edits without the user re-attaching the project'). It also names the counterpart tool (osirAppDeploy) and osirAppList for the appName, so the agent can place it in the workflow without opening a 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?

Explicit branching guidance: inline=true is recommended for patching, inline omitted yields only a signed zip URL that is 'useful only to a client with a shell'. It also states the when-not condition ('If truncated=true ... do NOT redeploy from them') and the follow-up requirement to deploy ALL files under the SAME name.

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.