Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Run many Luau snippets in order in one call

batch-execute
Destructive

Run several independent Luau snippets in one round trip, collecting each result and isolating per-snippet compile or runtime errors so one failure never aborts the rest.

Instructions

Run several independent Luau snippets in sequence in a single round trip, collecting every result without paying a separate tool call per snippet. Each snippet is COMPILED with loadstring and run under its own pcall, in input order; a compile or runtime error in one snippet is recorded for that snippet only and never aborts the others. For each snippet you get { index, ok, value? , error? } — value is the FIRST return value, encoded so Instances/Vector3/etc. survive serialization; error carries the compile or runtime message when ok is false. Use this to read several instances, probe multiple remotes, or run a short script of steps in one shot. Requires loadstring (guarded). Returns { results = [{ index, ok, value?, error? }] } in input order. Signature: { snippets: {string}, client: string?, agent: string?, threadContext: number?, timeoutMs: number? }. Phase: orchestrate; cost=medium; idempotency=contextual-write. Requires: active-client, explicit-mutation-approval. Produces: operation-receipt. Verify with: assert-state. Safety: MUTATING; executes caller-selected behavior in the live client. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNoOptional. A stable label for WHICH agent is calling when several share this MCP session (e.g. 'researcher'). Gives that agent its own fair scheduling lane, its own persistent VM on each game, and its own queue budget, so co-tenant agents don't starve or clobber each other.
clientNoOptional. Run on a specific connected client — its clientId OR username — for THIS call only, overriding your session's select-client binding without changing it. Lets multiple agents drive different games at the same time; omit to use your session's selected client.
snippetsYesThe Luau snippets to run, in order. Each is compiled and pcall-guarded independently; to capture a value, `return` it (only the first return value is collected).
timeoutMsNoOptional per-call deadline in milliseconds; omit it to use the tool or server default.
threadContextNoOptional Roblox thread identity for this call; omit it to use the server default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-spies.2

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds the annotations: it discloses per-snippet loadstring compilation, independent pcall isolation, that one error never aborts the batch, input-order guarantees, serialization-safe value encoding, the guarded loadstring requirement, and the mutation/approval/safety profile. This is exactly the behavioral context annotations alone (destructive/readOnly hints) cannot convey.

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 and ordered logically, but the result shape is effectively stated twice ({ index, ok, value?, error? } and Returns { results = [...] }), which is mild redundancy rather than waste.

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

Completeness5/5

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

No output schema exists, and the description compensates fully by documenting the return shape, ordering, error isolation, and prerequisites. Nothing an agent needs to invoke it correctly is missing.

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, but the description adds real semantics: only the FIRST return value is collected, snippets execute in input order, and the value is encoded so Instances/Vector3 survive. That meaning goes beyond the raw schema descriptions.

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?

States a specific verb and resource ('Run several independent Luau snippets in sequence in a single round trip') and immediately frames the distinction from single-snippet siblings: one call instead of a separate tool call per snippet. An agent can tell it apart from execute/run-luau 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 Guidelines4/5

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

Gives concrete usage contexts ('read several instances, probe multiple remotes, or run a short script of steps in one shot') and states the requirement of loadstring. It does not explicitly name alternatives like execute or run-luau and when NOT to batch, so it stops short of full when/when-not guidance.

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

Deploy Server

Other Tools