Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx

Search the GC heap for where a value is stored (Cheat-Engine scan)

search-gc-value
Read-onlyIdempotent

Find where values like coin/HP totals, remote names, toggles, or object references live in Roblox Luau GC memory, then report matching keys, values, constants, and upvalues.

Instructions

Cheat-Engine-style heap scanner: find WHERE a specific value lives across the entire Luau garbage collector. Resolve a target from one of five value types, then walk every live object via getgc(true) and report each place that holds it. For GC TABLES the tool pcall-iterates pairs() and records a hit when a KEY or a VALUE matches (string matches support exact OR 'contains' substring search). For Lua CLOSURES (when scanFunctions is on) it scans the function's constants and upvalues. Each match reports { container, where, keyText? } where 'where' is one of value/key/constant/upvalue and 'container' is the table address or the closure's source:line. Use it to locate a coin/HP total, a remote or flag name, a boolean toggle, or a Part/Instance reference, then pivot with inspect-closure / dump-table / set-closure-upvalue to read or mutate it. Requires getgc; closure scanning additionally requires getconstants/getupvalues (each is type-guarded and simply skipped if the executor lacks it). Everything is pcall-guarded so locked/dead objects never abort the scan; the object count is capped by maxScan and the result list by limit, with a 'truncated' flag. Returns { valueType, matchCount, truncated, matches } or { error }. Signature: { valueType: "number" | "string" | "boolean" | "instance" | "raw", value: string | number | boolean?, match: any?, scanFunctions: any?, limit: any?, maxScan: any?, threadContext: number? }. Phase: observe; cost=medium; idempotency=read-only. Requires: active-client. Capabilities: getgc. Produces: bounded-candidates. Safety: read-only. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax number of match locations to return (default 150). Hitting this sets truncated=true.
matchNoMatch mode (default 'exact'). 'contains' performs a plain (non-pattern) substring search and applies ONLY to string searches; for every other value type it is ignored and exact equality is used.exact
valueNoThe value to search for. For number/string/boolean this is the literal value. For 'instance' it is a Luau path expression resolving to an Instance. For 'raw' it is a Luau expression that is evaluated and whose result is the search target. Required for instance/raw; for number/string/boolean it may be omitted only if you really mean to search for the empty string / 0 / false (prefer always supplying it).
maxScanNoMax number of GC objects (tables + functions) to examine before stopping (default 40000). Hitting this sets truncated=true. Raise for a more thorough sweep at the cost of time; lower it if scans are slow.
valueTypeYesHow to interpret 'value' and what to search for: - 'number': search for a numeric value (e.g. a coin/HP total). - 'string': search for a string (supports match='contains' for substrings — e.g. a remote name). - 'boolean': search for true/false (e.g. a god-mode flag). - 'instance': 'value' is a Luau path/expression resolving to an Instance (e.g. 'game.Workspace.Boss'). - 'raw': 'value' is an arbitrary Luau expression; the tool searches for whatever it evaluates to (e.g. 'Enum.KeyCode.E', 'Vector3.new(0,0,0)', 'game:GetService("Players").LocalPlayer').
scanFunctionsNoAlso scan Lua closures' constants and upvalues for the target (default true). Disable to scan tables only, which is faster and avoids getconstants/getupvalues overhead.
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?

Beyond the read-only/idempotent annotations it discloses a great deal of behavioral detail: pcall-guarded traversal so dead/locked objects never abort, type-guarded getgc/getconstants/getupvalues that skip silently, table pair-iteration vs closure constant/upvalue scanning, and truncation via limit/maxScan. This is well past what the annotations 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 purpose and scan mechanics before usage and prerequisites, and most sentences carry information. It is somewhat long and the tail (Signature restatement, phase/cost/idempotency, capabilities, safety) partly duplicates the schema and annotations rather than adding to them.

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 supplies the return shape ({ valueType, matchCount, truncated, matches } or { error }), the getgc dependency plus optional getconstants/getupvalues, the active-client requirement, and the truncation behavior. An agent can call and interpret it correctly without opening other artifacts.

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 meaningful semantics: match='contains' applies only to strings and is ignored otherwise, and value semantics per valueType (Luau path for instance, evaluated expression for raw). It also describes the match record shape { container, where, keyText? }, which is not in any schema.

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: find WHERE a value lives across the Luau garbage collector, with five value types. Distinguishes itself from siblings like find-string-in-tables and find-tables-by-key by its value-type-driven, heap-wide scan scope.

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 use cases (coin/HP total, remote or flag name, boolean toggle, Part/Instance reference) and names the pivot tools (inspect-closure / dump-table / set-closure-upvalue) for follow-up. It does not explicitly contrast itself with nearby scanners like find-string-in-tables or scan-number-range, leaving that to inference.

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