Skip to main content
Glama

play

Start or stop a Roblox Studio test session and wait until Studio switches modes, or report the current mode.

Instructions

Start or stop a playtest (waits until Studio has actually switched), or report the current mode.

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": {
      "action": "<action>"
    },
    "name": "play"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important trait: start/stop block until Studio has actually switched, which tells the agent to expect a synchronous wait. It omits error conditions, idempotency of repeat start/stop calls, and whether the operation can fail on timeout.

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

Conciseness5/5

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

A single front-loaded sentence covering all three modes, with the blocking behavior in a parenthetical where it does not disrupt scanning. Nothing is wasted.

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?

For a 2-parameter tool with no output schema and no annotations, the description should say what 'current mode' actually returns and what happens on a failed or repeated transition. The blocking note helps, but return values and failure behavior remain unspecified.

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 50% and the studio parameter already documents itself as optional with name-substring/place-id/id forms. The description adds only the implicit mapping of status to 'current mode'; it says nothing about how studio interacts with start/stop beyond the schema's own text. Baseline 3 fits.

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?

The description names a specific verb set and resource: start/stop a playtest, or report current mode. All three actions map cleanly onto the action enum, so an agent knows exactly what the tool covers. It stops short of a 5 because it never distinguishes itself from other playtest-adjacent tools in the catalog.

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

Usage Guidelines3/5

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

The action names imply when each is used (start to begin, stop to end, status to check), but the description gives no explicit when-to-use guidance, no prerequisites, and no mention of what to do when a playtest is already running. The only concrete routing hint lives in the studio parameter schema, not the description.

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