Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete a folder from the executor workspace (UNC delfolder)

delete-folder
Destructive

Permanently deletes a folder and its contents from the executor's workspace. This destructive operation cannot be undone.

Instructions

Delete a folder (and typically its contents) from the executor's workspace. NOTE: this is executor-side file I/O — the connector runs INSIDE the executor, so the path is relative to the executor's workspace directory on the host machine, NOT the Roblox game. This is destructive and recursive on most executors; it cannot be undone. Requires the UNC function delfolder(path). The call is type-guarded and pcall-wrapped: if delfolder is missing you get { error = 'delfolder is not available in this executor.' }, and any failure (missing folder, permission) returns { error = }. Returns { path, ok = true } or { error }. Signature: { path: string, threadContext: number?, timeoutMs: number? }. Phase: act; cost=medium; idempotency=contextual-write. Requires: active-client, resolved-target, explicit-mutation-approval. Capabilities: executor filesystem. Produces: operation-receipt. Verify with: file-exists. Safety: MUTATING; writes executor workspace filesystem. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the folder to delete within the executor workspace, e.g. 'data/snapshots'.
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.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that deletion is recursive on most executors, irreversible, type-guarded and pcall-wrapped, with concrete error payloads and return shapes. Annotations cover the safety flags but the description adds substantial operational detail.

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?

Purpose and the critical NOT-the-game warning are front-loaded, and the metadata (phase, idempotency, requires, produces) is organized. It is dense and includes some boilerplate, but every part is scannable and earns its place.

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?

With no output schema, the description fully specifies return values, error cases, prerequisites, and a verification tool. 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.

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 path, timeoutMs, and threadContext. The description restates the signature and the executor-relative path semantics, adding little beyond what the schema provides — baseline 3.

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 (delete) and resource (folder) with explicit scope: the executor's workspace, not the Roblox game. This cleanly distinguishes it from siblings like delete-file and destroy-instance.

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?

Provides clear context (executor-side file I/O, phase=act, requires explicit-mutation-approval) and a verification path (file-exists). It implies when to use it, but does not explicitly contrast against delete-file for the folder-vs-file decision.

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