Run Luau code in 2021 Roblox Studio's edit context and return the output. Use it to test scripts, automate edits, or inspect results from an AI coding assistant.
Executes Luau code in 2021 Roblox Studio edit context and returns output
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | Luau code to run in Studio |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. For an arbitrary code-execution tool it omits critical traits: whether execution is sandboxed, whether it can mutate the Studio document, permissions required, error/failure behavior, or runtime limits. It only says it runs in edit context and returns output.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence with the operation and context front-loaded. No wasted words, though it is arguably too terse given what it leaves unsaid.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a high-risk arbitrary-code-execution tool with no annotations and no output schema, the description is too thin. It should disclose side-effect potential, sandboxing/editing semantics, and output format expectations to be complete enough for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter and schema description coverage is 100%, so the schema already documents the code argument. The description adds no syntax, format, or size constraints beyond what the schema provides; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Executes) and resource (Luau code) and pins the execution context (2021 Roblox Studio edit context) and that it returns output. This clearly distinguishes it as the only arbitrary-code-execution tool among siblings like read_script or create_instance, though it does not name those siblings explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus the more targeted siblings (read_script, write_script, create_instance, get_tree). An agent must infer that this is the escape hatch for operations the structured tools don't cover.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.