Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_multiplayer

Start, add players to, leave, end, or check the state of a Roblox Studio multiplayer playtest session to test gameplay with multiple clients.

Instructions

Multiplayer playtest: start|add|leave|end|state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "roblox_multiplayer"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNostate
playersNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It lists action names but does not disclose whether actions mutate state, what side effects occur, whether permissions or prerequisites are required, or how destructive 'end' and 'leave' are.

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

Conciseness3/5

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

The definition is a single front-loaded line with no wasted prose, but it is under-specified rather than genuinely concise. The pipe-separated action list is readable, yet the overall structure omits nearly all decision-relevant context.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. However, with no annotations and 0% schema description coverage, a stateful multiplayer lifecycle tool needs much more than a list of action names to be callable correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It lists possible action values, which adds some meaning beyond the bare schema, but it completely omits the 'players' parameter's purpose and behavior.

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 description identifies the domain as a multiplayer playtest and lists lifecycle actions, but it never states a clear verb or object such as 'manage a multiplayer playtest session.' It vaguely distinguishes multiplayer from single-player siblings by name, yet an agent cannot tell precisely what 'add' or 'leave' operate on.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as roblox_playtest or roblox_solo. The action tokens imply a lifecycle sequence, but the description never says when to choose 'start' versus 'add' or how this differs from other playtest tools.

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