Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Replicate a signal to the SERVER

replicate-signal
Destructive

Fires a Roblox signal to the server with full network replication after verifying it is replicable, enabling authorized server-side effect testing. Refuses non-replicable signals.

Instructions

MUTATES SERVER STATE — DANGEROUS. Invokes replicatesignal(signal, ...) to fire the event with full network REPLICATION, so the event is delivered to the SERVER and can have real, authoritative server-side effects (unlike fire-signal, which is local only). Only some signals are replicable; this tool first checks cansignalreplicate(signal) and refuses to fire if it returns false. Use this ONLY for authorized testing of a game you own/control — firing replicated signals on other games may violate their rules. Requires the executor's replicatesignal; degrades with a clear { error } if unavailable. Returns { Signal, Instance?, Replicated, ArgCount } or { error }. Signature: { instancePath: string, signalName: any?, args: {{ kind: "string" | "number" | "boolean" | "nil" | "instance" | "raw", value: string | number | boolean? }}?, threadContext: number? }. Phase: act; cost=medium; idempotency=contextual-write. Requires: active-client, resolved-target, explicit-mutation-approval. Capabilities: getconnections, firesignal. Produces: structured-result. Verify with: assert-state. Safety: MUTATING; writes live game/client state. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoOrdered list of arguments to replicate with the event, mirroring the real arguments the server expects for this signal. Omit or pass [] to replicate with no arguments.
signalNameNoName of the RBXScriptSignal member on the instance (e.g. 'OnClientEvent'). Leave empty/omit if instancePath already evaluates to the signal.
instancePathYesLua expression resolving to the Instance that owns the signal (e.g. 'game.ReplicatedStorage.RemoteEvent'). Evaluated as `return <instancePath>`. Leave signalName empty if this expression already resolves to the signal itself.
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?

Annotations already declare destructive=true and idempotent=false, but the description adds substantial extra context: it requires the executor's replicatesignal, degrades to a clear { error } if unavailable, refuses when cansignalreplicate is false, and has authoritative server-side effects. This goes well beyond the safety profile the annotations provide.

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?

The dangerous-mutation warning and the fire-signal contrast are front-loaded, which is exactly right. However, the trailing template metadata (Phase/cost/idempotency/Requires/Capabilities/Produces/Verify/Safety) partially duplicates the opening 'MUTATES SERVER STATE — DANGEROUS' warning, adding some bulk.

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?

Although there is no output schema, the description discloses the return shape ({ Signal, Instance?, Replicated, ArgCount } or { error }), the failure mode, prerequisites, and invocation signature. Nothing an agent needs to call this 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 description coverage is 100%, so the schema already documents all four parameters in detail. The inline signature and notes (e.g. omitting args, threadContext default) largely restate what the schema provides rather than adding new semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (replicate/fire with network replication) and resource (signal to the SERVER), and explicitly distinguishes itself from the sibling fire-signal ('which is local only'). An agent can tell exactly what this does and how it differs from the closest alternative without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it, the prerequisite (checks cansignalreplicate and refuses if false), and the exclusions ('ONLY for authorized testing of a game you own/control'). It also names the alternative fire-signal and the gating sibling can-signal-replicate, leaving nothing 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