Skip to main content
Glama

osirAppCreateUpload

osirAppCreateUpload: ONLY for a client with a shell and a project too large to send inline (over 500 files or 6 MiB). Usually you do NOT need this: call osirAppDeploy with the project's files directly. Returns an uploadTicket, a putUrl, and instructions to zip the project and PUT it there; then call osirAppDeploy with the uploadTicket. Requires authentication.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "osirAppCreateUpload"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (which only mark it non-read-only, non-destructive, non-idempotent), the description discloses the multi-step workflow, the returned artifacts (uploadTicket, putUrl, zip-and-PUT instructions), the required follow-up call, and the authentication requirement. The only notable omission is whether the ticket or putUrl expires, which matters for a non-idempotent two-phase upload.

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

Conciseness5/5

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

The restrictive qualifier 'ONLY' is front-loaded, followed by the default-path recommendation, then the return values and next step. Four dense sentences with no filler and a natural reading order that matches the agent's decision flow.

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?

There is no output schema, and the description compensates by naming the return fields and describing the PUT-then-redeploy sequence, so an agent knows what comes back and what to do with it. For a one-optional-parameter ticket-creation tool, nothing essential 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?

There is a single optional parameter, sessionKey, and schema description coverage is 100%, so the schema already explains the osk_ prefix and the OAuth-vs-device-flow distinction. The description adds no parameter-level meaning beyond that, so the baseline of 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?

The description gives a specific verb and resource ('create upload ticket' for an app project) plus the exact scope that distinguishes it from siblings: only for shell-capable clients with projects over 500 files or 6 MiB. An agent can tell immediately this is not the normal deploy path.

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?

It names the default alternative explicitly ('Usually you do NOT need this: call osirAppDeploy with the project's files directly') and states the precise preconditions that select this tool instead. The when-not and the numeric thresholds are both spelled out, leaving nothing to inference.

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.