Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Walk a thread/coroutine's call stack

get-thread-stack
Read-onlyIdempotent

Walk a Luau thread or coroutine's call stack frame by frame to see exactly where it is executing; omit the thread path to inspect the current thread.

Instructions

Walk the call stack of a Luau thread/coroutine frame-by-frame using debug.info. For each level it reports the function Name, Source, and Line (debug.info(thread, level, 'nsl')), stopping when the stack is exhausted. If threadPath is omitted it traces the CURRENT injected thread instead, using debug.info(level, 'nsl'). A debug.traceback() string is also included when available. Use this to see exactly where a suspended coroutine or an event handler's thread is currently executing — e.g. pass a connection's .Thread, a stored coroutine, or leave it blank to inspect your own execution context. WARNING: this ACTS ON THE LIVE GAME — it evaluates your threadPath expression and introspects live thread state in the running client. Returns { Thread?, FrameCount, Frames:[{ Level, Name, Source, Line }], Traceback? } or { error }. Signature: { threadPath: string?, maxLevels: any?, threadContext: number? }. Phase: observe; cost=medium; idempotency=read-only. Requires: active-client, resolved-target. Produces: structured-observation. Safety: read-only. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxLevelsNoMaximum number of stack levels to walk before stopping (default 20, max 60). Walking stops early once debug.info returns nil for a level (top of stack reached).
threadPathNoOptional Luau expression resolving to a thread/coroutine, e.g. 'getconnections(game.Workspace.Part.Touched)[1].Thread', 'getgenv().myCoroutine', or 'coroutine.running()'. Evaluated as `return <threadPath>`. If omitted, the current injected thread is traced instead.
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.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that the call evaluates the threadPath expression against live game state, warns that it acts on the live client, explains the omission behavior (traces the current injected thread), and includes the return shape and optional traceback.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and usage are front-loaded well, but the tail ('Phase: observe; cost=medium; ... Requires: active-client ... On failure: inspect tool-schema ...') largely restates annotation metadata and adds boilerplate that does not earn its place.

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 exists, but the description supplies the return shape ({ Thread?, FrameCount, Frames, Traceback? } or { error }) and covers safety, prerequisites, and failure handling, so an agent has enough to call it correctly; only minor edge behavior is left implicit.

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 description coverage is 100%, so the schema already documents threadPath, maxLevels, and threadContext. The description reinforces the omitted-threadPath behavior but adds little syntax or constraint detail beyond the schema, matching the 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 and resource ('Walk the call stack of a Luau thread/coroutine frame-by-frame using debug.info') and scopes it precisely to thread/coroutine introspection, distinguishing it from generic stack siblings like get-call-stack and get-stack.

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 context ('see exactly where a suspended coroutine or an event handler's thread is currently executing') plus worked examples (pass a connection's .Thread, a stored coroutine, or leave blank). It does not explicitly name an alternative tool or a when-not-to-use condition, so it stops 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