Skip to main content
Glama

Host the game at a share link

publish_game
Idempotent

Host the game's files at a public share link, https://.play.multiplayeragent.com/ (the game's own origin; the slug comes from the game's name and never changes). The game needs an index.html at the root plus any JS/CSS/assets, paths relative to it. Send small text files (HTML, JS, CSS, JSON) inline as { path, content }. For images, audio, fonts, models and ANY file over ~50 KB, call create_upload first, PUT each file with curl, and pass { path, uploadId } here: the bytes never go through you. (Inline base64 with encoding: "base64" still works for a tiny binary.) The files must use THIS game's publishable key (it is how the server knows the build belongs to this game; a client wired to another game is refused). mode "replace" (the default) makes the files you send the whole game: anything not sent is removed. mode "patch" adds or replaces only the files you send and keeps the rest, and remove deletes paths: use it to fix one file without resending the art, or to put a big build up over several calls. Re-run after every change; the link stays the same. Limits on this studio's plan: 100 files and 5 MB per game, 25 MB across all its games. Give the user the url: anyone who opens it joins the same rooms. Nothing is listed publicly; only people with the link find it.

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": {
      "files": "<files>"
    },
    "name": "publish_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoWhich game to act on: its publishable key (pk_…) or its exact name. Defaults to the x-mp-game header, then your primary game.
modeNo'replace' (default): these files become the whole game. 'patch': add or replace just these, keep everything else hosted.
filesYesThe files: in replace mode every file of the game, including index.html; in patch mode just the ones to add or replace.
removeNoPatch mode only: hosted paths to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"Every file of the game, including index.html."New value: +"The files: in replace mode every file of the game, including index.html; in patch mode just the ones to add or replace."
    • changedInput schema / properties / files / items / properties / content / description
      Previous value: -"The file's content: the text itself, or base64 when encoding is 'base64'."New value: +"Inline content: the text itself, or base64 when encoding is 'base64'. For small text files; use uploadId for anything else."
    • changedInput schema / properties / files / items / properties / encoding / description
      Previous value: -"'utf8' (default) for text files; 'base64' for binaries."New value: +"'utf8' (default) for text files; 'base64' for an inline binary."
    • addedInput schema / properties / files / items / properties / uploadId
      Added value: +{
      +  "description": "Instead of content: an uploadId from create_upload, for this game, whose curl PUT has finished.",
      +  "type": "string"
      +}
    • changedInput schema / properties / files / items / required
      Previous value: -[
      -  "path",
      -  "content"
      -]New value: +[
      +  "path"
      +]
    • removedInput schema / properties / files / minItems
      Removed value: -1
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "'replace' (default): these files become the whole game. 'patch': add or replace just these, keep everything else hosted.",
      +  "enum": [
      +    "replace",
      +    "patch"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / remove
      Added value: +{
      +  "description": "Patch mode only: hosted paths to delete.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 100,
      +  "type": "array"
      +}
  2. First observed

TDQS

A4/5.0
Behavior2/5

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

The description discloses rich behavior — plan limits (100 files, 5 MB/game, 25 MB total), the publishable-key ownership check, stable slug, and that the default replace mode REMOVES anything not sent. But annotations declare destructiveHint=false while replace mode explicitly deletes hosted files not included, which conflicts with that hint. Disclosure is otherwise strong, but the destructive-hint mismatch is a real inconsistency.

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?

It is dense and long, but front-loads purpose and every sentence carries operative detail (URL, index.html requirement, upload flow, modes, limits). Slightly overpacked but no wasted filler.

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 complex deploy tool with no output schema, it covers the payoff (give the user the url), ownership constraints, mode semantics, upload flow, and limits — everything needed to invoke it correctly.

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 coverage is 100%, so mode, files, remove, and uploadId are already documented in the schema. The description corroborates mode semantics and the uploadId workflow but adds little beyond what the schema provides; baseline 3 applies when the schema does the heavy lifting.

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 opening sentence states a specific verb and resource ('Host the game's files at a public share link') and immediately names the origin/URL and slug semantics. An agent can distinguish this deployment action from create_upload or deploy_room_logic without opening the 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?

It explicitly routes between alternatives: send small text inline, but for binaries/large files 'call create_upload first, PUT each file with curl, and pass { path, uploadId } here'. It also spells out when to use replace vs patch vs the remove field (fix one file, or put a big build up over several calls).

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.