Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx

Watch any Luau expression over time (live value monitor)

watch-value
Read-onlyIdempotent

Sample any Luau expression over a bounded window, logging every value and exact change times to verify, time, or debug in-game state.

Instructions

Sample ANY Luau expression repeatedly over a bounded window and report every value it took plus exactly when it changed — a live memory/state monitor for reverse-engineering and debugging. Give an expression that returns a value (no return keyword needed) and the tool compiles it once with loadstring, then polls it on a fixed interval until the duration elapses, recording the first sample and every subsequent change. Use it to confirm a value actually mutates when you trigger an action (watch leaderstats coins tick up, a Humanoid's Health drop, an anti-cheat flag flip, a getgenv() speed multiplier, a remote-cooldown timer, or a metatable hook's hit counter), to time how fast something updates, or to prove a suspected variable is the one that drives a behavior. EXAMPLES: 'game.Players.LocalPlayer.leaderstats.Coins.Value', 'getgenv().speed', 'workspace.CurrentCamera.CFrame.Position', '#getconnections(game.Workspace.Part.Touched)', 'tostring(getgenv().__mcp_remotespy and #getgenv().__mcp_remotespy.logs)'. The expression is evaluated as return <expression>, so it can be any value-producing Luau (indexing, function calls, arithmetic, concatenation). Each sample is stringified for transport (Instances become GetFullName()). Change detection compares the live value with the previous one via ~=, so it catches identity changes for tables/Instances and equality changes for scalars. IMPORTANT: this call BLOCKS in-client for roughly durationMs while it samples (it is inherently synchronous), so keep durations short and perform the triggering action shortly before or during the watch. Everything is fully pcall-guarded: a compile error returns { error } immediately, and a per-tick evaluation error is recorded as a sample value rather than aborting the loop. Returns { expression, intervalMs, durationMs, sampleCount, changeCount, truncated, samples = [{ t, value, changed, ok }] }. Signature: { expression: string, intervalMs: any?, durationMs: any?, threadContext: number? }. Phase: observe; cost=medium; idempotency=read-only. Requires: active-client. Produces: bounded-event-snapshot. Safety: read-only. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
durationMsNoTotal time to watch in milliseconds (default: 5000, clamped 50..30000). The call blocks in-client for about this long; the network timeout is set to durationMs + 10000 so the loop finishes before the round-trip times out.
expressionYesAny Luau expression that returns a value (do NOT prefix with `return` — the tool adds it). Examples: 'game.Players.LocalPlayer.leaderstats.Coins.Value', 'getgenv().speed', 'workspace.CurrentCamera.FieldOfView', '#getconnections(game.Workspace.Part.Touched)'.
intervalMsNoPolling interval in milliseconds between samples (default: 200, clamped 20..5000). Smaller catches fast transitions but produces more samples and more in-client 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.1/5.0
Behavior5/5

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

Discloses far more than the annotations: the call BLOCKS in-client for ~durationMs (synchronous), is fully pcall-guarded, returns { error } on compile failure, records per-tick evaluation errors as sample values, detects change via ~=, and stringifies values (Instances become GetFullName()). These are exactly the operational behaviors annotations cannot convey.

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?

Front-loads what it does well, but is long and carries redundant tail metadata that restates the annotations (idempotency=read-only, Safety: read-only, Requires/Produces) alongside a repeated signature block. Informative but not tight; several lines could be trimmed without loss.

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?

No output schema is present, but the description fully specifies the return shape (expression, intervalMs, durationMs, sampleCount, changeCount, truncated, samples with t/value/changed/ok), the blocking constraint, and error semantics. An agent has everything needed to call and interpret it.

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 all four parameters (including clamps and defaults) are already documented. The description reinforces expression semantics ('evaluated as return <expression>') and the polling model, but this largely duplicates the schema rather than adding new meaning, matching the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (sample/watch) and resource (ANY Luau expression over a bounded window), plus the underlying mechanism (loadstring + fixed-interval polling). The emphasis on 'ANY expression' implicitly sets it apart from the property-specific watchers, but no sibling is named explicitly, which is what separates a 4 from a 5.

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?

Offers concrete when-to-use triggers: confirm a value mutates when you act, time how fast something updates, or prove a variable drives behavior, with realistic worked examples. It stops short of explicit exclusions or named alternatives (e.g. when to prefer watch-instance-property over this generic watcher), leaving that inference to the agent.

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