Skip to main content
Glama

remix_game

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Makes a remix of a game on YouGame for the creator: a copy of that game's latest build, under the terms its creator set (shown on https://yougame.co/g//remix), published at once as a new game of the creator's own. Needs the creator's API key or sign-in, and a game whose creator allows remixes. The remix starts as a minor variant, available from the original game rather than discovery; a remix of a private game starts private, seen only by its creator until they make it public on its Manage page (the original's testers are not added). For substantially different gameplay, upload the changed build, then choose Major remix on its Manage page with a distinct title and thumbnail. The reply has the new game's slug and a download link for its build (GET it with the same Authorization header): download the zip, make the changes, and ship them with update_game on the new slug. Keep every YouGame.coins.charge call the build has, or the update is refused.

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": "remix_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe game to remix: the last part of its URL, https://yougame.co/g/<slug>.
titleNoThe remix's title, 1–80 characters. Default: the original's title followed by “remix”.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false, idempotent=false) by disclosing that the remix starts as a minor variant discoverable only from the original, that a remix of a private game starts private with the original's testers excluded, and that the update is refused unless every YouGame.coins.charge call is preserved. It also states the reply shape (new slug plus build download link) even though no output schema exists.

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-loads the operation, then auth, then remix semantics, then the update workflow — a logical order with almost no filler. It loses a point for mild repetition, restating the auth requirement twice ('Needs sign-in (connect this server with OAuth...)' and 'Needs the creator's API key or sign-in') and packing multiple workflows into one dense block.

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 non-idempotent mutation with no output schema, the description covers the authentication requirement, the private/public visibility consequence, the returned slug and downloadable build, and the required follow-up via update_game. Nothing an agent needs to invoke it correctly or continue the workflow 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?

Schema coverage is 100%, so the slug URL fragment and the title default of '<original title> remix' are already documented in the schema; the description adds no new parameter-level detail such as format constraints or title-collision behavior. Baseline 3 is appropriate when the schema carries parameter meaning.

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 — 'Makes a remix of a game on YouGame for the creator: a copy of that game's latest build' — and immediately names the downstream sibling 'update_game on the new slug', so an agent can tell it apart from update_game, publish_game, and add_version without reading any 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?

Gives explicit preconditions (OAuth sign-in or Bearer API key, and a game whose creator allows remixes) and a branching rule: use this for a copy, but for 'substantially different gameplay, upload the changed build, then choose Major remix on its Manage page'. It also names the follow-up route via update_game, so both when-to-use and what-to-use-next are covered.

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