Skip to main content
Glama

sync_remix

Idempotent

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Brings the original's newest build into one of the creator's remixes, the way a branch is rebased on the branch it came from. Every remix records which build of its original it is based on; when the original ships a version, its creator is told and this tool (or the Bring in the update button on the remix's Manage page) does the merge: files the original changed that the remix left alone are taken, the remix's own changes stay, and the result ships as the remix's next minor version. Files both sides changed differently are conflicts: by default nothing changes and the reply lists them. Then either pass resolve "mine" (keep the remix's file for each conflict) or "theirs" (take the original's), or merge by hand: download the remix's build (GET /api/agent/download?slug=), the original's (…&build=parent) and, when it still exists, the base (…&build=base), three-way merge the conflicting files, upload the merged build like any update, and call update_game on the remix with upstream set to the original's build id from this reply (origin.upload_id), so the remix's base moves. Needs the creator's API key or sign-in.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe remix's slug: the last part of its URL, https://yougame.co/g/<slug>.
applyNofalse to only report the plan (what would be taken, kept, dropped, and the conflicts) without shipping anything. Default true.
resolveNoWhat to do with files changed on both sides: stop (default: report them, change nothing), mine (keep the remix's), theirs (take the original's).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses authentication requirements (OAuth sign-in or an Authorization: Bearer API key, and that the creator's key is needed), the default non-destructive failure mode (conflicts change nothing and are listed in the reply), the versioning effect (next minor version), and the state mutation when the manual path moves the remix's base. This is consistent with readOnlyHint=false and destructiveHint=false.

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 a dense single paragraph with almost no filler; every clause carries operational information. Structure is slightly weak because the authentication note is front-loaded ahead of the purpose statement, delaying the one-line answer to 'what does this do', but the manual-workflow tail is genuinely necessary for the conflict path.

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 merge/mutation tool with no output schema, the definition covers authentication, default behavior, conflict semantics, resolution options, versioning outcome, and the full manual merge procedure including the exact follow-up call and field (origin.upload_id). There is no output schema to describe, and the reply contents (conflict list, base id) are described inline.

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 description coverage is 100%, so the baseline is 3 and the schema already documents slug, apply, and the resolve enum. The description still adds genuine meaning: it explains what resolve does downstream (keeping the remix's file vs taking the original's, plus the manual three-way merge escape hatch) and that apply=false reports what would be taken, kept, dropped, and conflicted.

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 names a specific verb and resource with precise semantics: it brings the original's newest build into one of the creator's remixes, and defines exactly what merge means (files the original changed that the remix left alone are taken, the remix's own changes stay, result ships as the remix's next minor version). The rebase analogy plus the three-way merge detail makes it unambiguous against sibling update_game, which is explicitly named as the final step of the manual 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 states the triggering condition (the original ships a version, its creator is notified), offers the equivalent UI path (Bring in the update button), and gives explicit when-not behavior via apply=false to only report the plan. It also spells out the decision tree for the alternatives: stop by default, resolve mine/theirs, or do a manual merged upload followed by update_game with upstream set to origin.upload_id.

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