Skip to main content
Glama

native_upload_token

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Upload a native build (Windows, macOS or Linux) of your desktop-app listing: mint this single-use, game-bound token (2 hours), then use upload-native.mjs with YOUGAME_NATIVE_TOKEN. With request, an owner or maintainer answers that crowd request as a test branch beside live: on owner-governed games the owner or an approver puts it in from Feedback; community games merge by vote. For ordinary uploads the owner makes the build live from Manage → Desktop builds. For Unreal, upload a Shipping build.

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": {
      "slug": "<slug>"
    },
    "name": "native_upload_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhat is different in this build, which players read as what changed. Only letters, numbers, spaces and , ! ? ' ( ) - (no full stop or colon), starting with a letter or number; words like token, secret, password or hostname are refused.
slugYes
requestNoAnswer one open crowd request with a test build. Only the game's owner or maintainers may do this.
machine_labelNoA label you choose, such as Jam PC. Never a hostname or path.
source_commitNo
engine_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses that the token is single-use, game-bound, and expires in 2 hours, plus the OAuth/Bearer auth requirement. It also reveals the side effect of the request parameter — answering a crowd request as a test branch beside live, with owner/approver versus community-vote paths — which annotations do not cover.

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

Conciseness2/5

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

It is a single dense paragraph that interleaves authentication, token minting, upload tooling, crowd-request governance, release workflow, and engine-specific advice. Only the auth note is front-loaded; the actual purpose and parameter guidance are scattered mid-text, and several sentences describe operations this tool does not perform.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter mutation tool with no output schema, it covers auth, token lifetime, and the request path reasonably well, but it omits what the call returns (presumably the token value), leaves three parameters undefined, and blurs minting a token with performing an upload. The agent can call it, but must infer the response contract.

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 50%; the description adds real meaning for request (test branch beside live, restricted to owners/maintainers) and reinforces the note constraints. But slug, source_commit, and engine_version are undocumented in both schema and description, and the description never explains the relationship between the token and the game slug, so half the surface remains uninterpreted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The core action is stated ("mint this single-use, game-bound token (2 hours)"), but it is buried after an authentication preamble and surrounded by upload-workflow and crowd-request instructions. There is a sibling named upload_token and the description never distinguishes this tool from it, so an agent cannot route confidently on the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives downstream usage ("use upload-native.mjs with YOUGAME_NATIVE_TOKEN") and the condition for the request parameter ("Only the game's owner or maintainers may do this"), which is genuine when-to guidance. However, it never says when to choose native_upload_token over upload_token, and the workflow sentences about Manage → Desktop builds and Unreal Shipping builds describe what happens after an upload rather than when to call this tool.

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.

Resources