Skip to main content
Glama

cloud_luau

Destructive

Runs Luau scripts on a fresh server against your published Roblox place via Open Cloud, returning script results and print logs so you can verify production behavior without joining the game.

Instructions

Run server-side Luau against your PUBLISHED game via the Open Cloud Luau Execution API — a fresh ephemeral server loads the latest published place version, runs your script in SERVER context (require/ModuleScripts work; existing scripts do NOT auto-run; no physics), and returns the script's return values + print logs. The closest thing to 'verify in production' without joining the game. ⚠ NOT a side-effect sandbox: DataStoreService and HttpService ARE available and PERSIST (a script could even AssetService:SavePlaceAsync) — runtime/in-memory state is throwaway, but cloud writes are real. Long scripts: if still running when the wait elapses, re-call with resume = the returned task path. Needs an Open Cloud key with the luau-execution scope (TUFAN_OPENCLOUD_KEY) + a published universe. For Studio EDIT-mode code use run_luau instead; for code inside a live Studio play session use Roblox's official Studio MCP (execute_luau).

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": "cloud_luau"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
resumeNoa task path from a previous call to keep polling (instead of creating a new task)
scriptNothe Luau to run (end with `return ...` for values back). Omit when resuming.
versionIdNopin a specific published place version (default: latest)
waitSecondsNohow long to poll before returning the task path (default 60)
timeoutSecondsNomax script runtime on the server (default/max 300)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that existing scripts do not auto-run, no physics, runtime/in-memory state is throwaway, but DataStoreService/HttpService writes persist and AssetService:SavePlaceAsync is possible — consistent with destructiveHint=true and openWorldHint=true. The main thing left implicit is the response envelope shape when a task is still running, though the resume hint partially covers it.

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?

Front-loaded with the core behavior, then the side-effect warning, then the long-script resume note, then the sibling routing — a defensible order for a risky tool. The prose is dense and every sentence carries information, though the parenthetical caveats make it longer than strictly necessary.

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

Completeness4/5

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

Even without an output schema the description states what comes back (script `return` values plus print logs, or a task path when polling times out), and the persistence warning is precisely the safety context an agent needs before invoking a destructive, open-world tool. Only the exact shape of a pending-task result is left to inference.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds cross-parameter meaning by explaining that `resume` takes the task path from a previous call when the `waitSeconds` window elapses, which the per-property docs do not connect. Field-level syntax (e.g. place formats, versionId semantics) is left entirely to the schema.

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

Purpose5/5

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

A specific verb and resource ('Run server-side Luau') plus the exact execution environment: published place version, fresh ephemeral server, SERVER context, return values and print logs. It explicitly separates itself from run_luau and the official Studio MCP execute_luau, so an agent can pick correctly without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules: use run_luau for Studio EDIT-mode code, Studio MCP execute_luau for code inside a live play session, and this tool for verifying against a published universe. It also states prerequisites (Open Cloud key with luau-execution scope, published universe) and when to re-call with `resume`.

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