Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_solo

Start or stop a solo playtest in Roblox Studio to test gameplay changes in isolation. Use mode play to begin and mode stop to end the session.

Instructions

Start/stop solo playtest: mode play|stop.

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_solo"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoplay

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/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 signals that this is a state-changing, dual-mode tool (start vs. stop) and that the default is "play", but says nothing about whether stopping terminates a running session, whether it requires a prior play, or what happens on failure.

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?

One short, front-loaded sentence with the action pair and the parameter values in a compact form; nothing is wasted. It is telegraphic, but the truncation costs a little clarity rather than adding filler.

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

Completeness3/5

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

The tool is simple (one optional parameter, output schema present so return values need not be described), so a terse definition is defensible. However, for a mutation tool with zero annotation coverage and an undocumented parameter default, the description leaves the side effects of "stop" and mode precedence unstated.

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 description coverage is 0% and the single parameter has no enum defined, so the description's "mode play|stop" is genuinely the only source of the accepted values. It still omits the default value (play) and the effect of each mode.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Start/stop solo playtest" gives a specific verb pair and resource, and the word "solo" distinguishes it from the roblox_playtest and roblox_multiplayer siblings without naming them. It is clear what the tool does, though it does not explicitly contrast itself with roblox_playtest.

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?

Nothing states when to choose solo playtesting over roblox_playtest or roblox_multiplayer, nor any precondition such as needing a built/ready place. The mode values imply the two actions but give no conditions for either.

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