Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Reset the Persistent Script VM

vm-reset
Read-onlyIdempotent

Clear the persistent VM environment for the script tool, discarding globals and functions from prior runs to start a clean session without touching the game.

Instructions

Wipe the persistent VM environment used by the script tool. Every global, function, and value defined by previous persistent script runs is discarded, giving you a clean session. This does NOT touch the game itself — only the VM's own sandboxed environment. Wipes ONLY your own scope: pass the same agent label (and client) you run scripts under so it clears that agent's VM on that game, never a co-tenant's. Returns { reset = true }. Signature: { client: string?, agent: string? }. Phase: observe; cost=medium; idempotency=read-only. Requires: active-client. Produces: operation-receipt. Safety: read-only. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNoOptional. Reset the persistent VM belonging to this agent lane — pass the SAME label you run your `script`/`execute` calls under, so you clear your own VM and not a co-tenant agent's.
clientNoOptional. Reset the VM on a specific connected client (its clientId or username) for THIS call, instead of your session's selected client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-spies.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false; the description adds real context beyond them — exactly what gets discarded (all globals/functions/values), that the game is untouched, scope isolation per agent/client, and the return shape { reset = true }. Some inline metadata (Phase/cost/Safety) restates annotation hints redundantly.

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 action and scope, then constraints. It is somewhat long and ends with a dense metadata tail (Phase/cost/idempotency/Requires/Produces) that is partly redundant with annotations, diluting conciseness.

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?

No output schema, but the description supplies the return value, required active-client precondition, failure guidance, and safety scoping — enough for an agent to call it correctly. Remaining gap is minimal.

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% (baseline 3), and the description adds meaning: `agent` must match the label scripts run under to avoid clearing a co-tenant, and `client` overrides the session's selected client for this call. This clarifies intent beyond the schema text.

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?

The first sentence states a specific verb and resource ('Wipe the persistent VM environment used by the `script` tool') and ties it to the relevant sibling (`script`). An agent immediately understands this resets persistent script state rather than touching the game.

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?

It gives clear operational guidance: pass the same `agent`/`client` you run `script`/`execute` under so you clear your own lane, not a co-tenant's. It does not explicitly contrast with alternate VM tools (e.g. new-lua-state-proxy), but the when/how context is strong.

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