Skip to main content
Glama
Sign In

Multiplayer Agent

by com.multiplayeragent
OverviewDiscussionsAdmin

Start a new game from a starter

remix_game

Start from a starter game (see list_starters): makes a NEW game in this studio (or, with game, reuses one of yours) and returns a link to the starter's source as a ZIP, valid for 5 minutes, plus the steps to unpack it, rewire it to the new game's publishable key, and publish it. Premium starters need a paid plan; a locked one returns the upgrade link instead, and nothing is created.

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": {
      "starter": "<starter>"
    },
    "name": "remix_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoReuse one of your games instead of making a new one (its pk_ or exact name): e.g. to fetch a fresh link after one expired.
labelNoA name for the new game. Defaults to the starter's title.
starterYesThe starter's slug, from list_starters, e.g. 'slither-arena'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only flag the write/open-world/non-idempotent profile, but the description adds what actually happens: a ZIP link to the starter source valid for 5 minutes, plus unpack, rewire, and publish steps. It also covers the premium-plan gate and that a locked starter returns an upgrade link with nothing created, which is behavior beyond the structured fields.

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-loaded with the purpose, then the return value, then the edge cases. It is dense and leans on one long clause chain with parentheticals, but each clause carries distinct information.

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?

With no output schema, the description carries the return burden and does so: ZIP link, 5-minute expiry, the unpack/rewire/publish steps, and the locked-starter outcome. Nothing needed to call it correctly or interpret the result 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 schema already documents all three parameters. The description only reinforces the starter-to-list_starters link and the `game` reuse case, both of which the schema states, so it adds little syntax or format detail beyond that baseline.

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: it starts a game from a starter, creates a NEW game in the studio, and points to list_starters for the source list. That distinguishes it cleanly from siblings like create_game or list_starters.

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

Usage Guidelines4/5

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

Explicitly routes the agent to list_starters before calling, and explains the `game` variant as the way to reuse an existing game (for example, to refresh an expired link). It doesn't contrast with create_game for a blank game, but the conditional guidance it does give is concrete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Multiplayer Agent toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources