Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_exec

Run Luau code in Roblox Studio’s edit, server, or client domain to test scripts and inspect runtime behavior.

Instructions

Execute Luau in edit/server/client domain.

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": {
      "source": "<source>"
    },
    "name": "roblox_exec"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoedit
sourceYes
confirmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it never says this executes arbitrary code with side effects on a live place. It hints at execution context via the domain list, but omits permission requirements, irreversibility, and what the 'confirm' gate actually guards against.

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 single sentence is front-loaded and free of padding, but it is under-specified rather than concise. Given the risk profile of arbitrary code execution, brevity here costs more than it saves.

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 the description is inadequate for a no-annotation tool that runs arbitrary code. It should at minimum explain the confirm gate and the consequences of each domain before an agent invokes it.

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 does implicitly enumerate the domain values (edit/server/client), which is genuine added meaning, but 'source' and especially 'confirm' (a safety flag defaulting to false) are left entirely undocumented.

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?

States a specific verb ('Execute') and resource ('Luau') plus the execution domains, so an agent knows this runs code rather than editing files. It does not distinguish itself from sibling tools such as roblox_script_edit, roblox_edit, or roblox_playtest, leaving overlap ambiguous.

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 guidance on when to prefer this tool over script-editing or playtest siblings, nor on prerequisites like a running session. The 'domain' choice (edit vs server vs client) is named but not explained as a decision the caller must make.

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