Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Dump the game or a subtree to the workspace (sUNC saveinstance)

save-instance
Destructive

Serialize an entire Roblox game or a chosen instance subtree to a file in the executor workspace, enabling backup or offline analysis. Set fileName and instancePath to control output.

Instructions

WRITES HOST FILES — serializes the entire game (or a chosen instance subtree) to a file in the executor's workspace folder via saveinstance. By default it dumps the whole DataModel; pass instancePath to dump just that subtree. This is a heavy operation that can take a while and produce a large file. Because executors differ on the exact signature, this tries several forms in order: saveinstance({ FilePath = fileName }), then saveinstance(instance, fileName) / saveinstance(instance), then saveinstance(). Requires saveinstance. The call is type-guarded and pcall-wrapped: if saveinstance is missing you get { error = 'saveinstance is not available in this executor.' }. Returns { saved, note } or { error }. Signature: { fileName: string?, instancePath: string?, threadContext: number?, timeoutMs: number? }. Phase: act; cost=medium; idempotency=contextual-write. Requires: active-client, resolved-target, explicit-mutation-approval. Produces: structured-result. Verify with: assert-state. Safety: MUTATING; writes live game/client state. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNameNoOptional output file name within the executor workspace (e.g. 'place.rbxm'). Omit to let the executor pick a default.
timeoutMsNoOptional per-call deadline in milliseconds; omit it to use the tool or server default.
instancePathNoOptional Luau expression for the instance to dump (e.g. 'game.Workspace'). Defaults to the whole game.
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.4/5.0
Behavior5/5

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

Annotations already declare destructive/non-idempotent/not-read-only, but the description adds substantial context beyond them: the multi-signature fallback strategy, pcall/type-guard wrapping, the exact error object returned when saveinstance is missing, the { saved, note } success shape, and the heavy/large-file caveat.

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?

The critical warning (WRITES HOST FILES) is front-loaded and each sentence carries distinct information. It runs long with the metadata tail (Phase/cost/Verify with), but nothing is redundant padding.

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?

For a mutating tool with no output schema, the description covers prerequisites, fallback invocation behavior, error and success payload shapes, and failure recovery (inspect tool-schema). An agent has everything needed to call it and interpret the result.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all four parameters. The description restates defaults (whole game when instancePath omitted, executor default fileName) but adds little syntax or constraint detail beyond the schema, so the baseline 3 applies.

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?

Opens with a specific verb+resource: 'serializes the entire game (or a chosen instance subtree) to a file in the executor's workspace folder via saveinstance.' This is clearly distinguished from siblings like write-file (arbitrary content) and get-instance-tree (inspection only).

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?

States the default behavior (whole DataModel) and the alternative trigger (pass instancePath for a subtree), plus the prerequisites (saveinstance availability, active-client, explicit-mutation-approval) and a warning that it is heavy/slow. It does not explicitly route away from alternative snapshot tools (e.g., diff-instance-snapshot or get-instance-tree), so it falls just short of 5.

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