Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_playtest

Runs a Roblox Studio playtest, captures screenshots and runtime logs, then verifies the outcome to diagnose gameplay issues.

Instructions

Screenshot + runtime logs, then verify verdict.

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

Input Schema

NameRequiredDescriptionDefault
cursorNo
instance_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2/5.0
Behavior1/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 and largely drops it. It does not say whether a playtest session is launched (a significant side effect), whether it blocks until completion, what permissions or instance state are needed, or how the 'verdict' is determined; the sequence wording is the only behavioral hint.

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?

It is a single compact phrase with no filler, so nothing is wasted, but at eleven words it is under-specified rather than concise. The artifact and the verify step are front-loaded in a readable order, which is the only structural strength.

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, but for a tool with two undocumented parameters and a multi-stage workflow the description leaves an agent unable to call it correctly. The critical gaps are invocation preconditions and the meaning of instance_id and cursor.

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

Parameters1/5

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

Schema description coverage is 0% for two parameters, and the description never mentions 'instance_id' or 'cursor', so an agent gets no guidance on which instance is targeted or what the cursor paginates or resumes. This is the exact case where the description must compensate and it does not.

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 phrase 'Screenshot + runtime logs' names concrete artifacts the tool produces, which goes beyond the bare name roblox_playtest, but 'then verify verdict' is undefined jargon and it is unclear what is being verified or against what. An agent can guess this captures playtest evidence but cannot confidently distinguish it from roblox_capture or roblox_profile.

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 statement of when to use this versus the many sibling capture/profile/build tools, and no prerequisites such as whether a running instance is required. The implied two-step workflow ('then verify verdict') hints at sequencing but names no conditions or alternatives.

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