Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Fire one specific connection on a signal

fire-connection
Destructive

Invoke a single Roblox signal connection's Fire or Defer handler by index, passing custom arguments to isolate and test one suspected handler without triggering all connections.

Instructions

MUTATES CLIENT STATE. Invokes a single connection's :Fire(...) (or :Defer(...) when defer=true) so that ONLY the one targeted handler runs with the supplied arguments — unlike fire-signal, which triggers every connection. Identify the connection by its index within getconnections(signal) (use list-signal-connections to find indices). This is client-side only and does not reach the server. Useful for isolating and testing a single suspected handler. The connection's Fire/Defer methods may be absent on foreign/C connections, so the call is pcall-guarded. Requires getconnections; degrades with a clear { error } if unavailable. Returns { Signal, Instance?, ConnectionIndex, Fired, Deferred } or { error }. Signature: { instancePath: string, signalName: any?, connectionIndex: any?, defer: 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. Produces: created-handle, operation-receipt. 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 pass to the targeted connection's handler. Omit or pass [] to fire with no arguments.
deferNoWhen true, call connection:Defer(...) to schedule the handler on the next resumption cycle instead of running it synchronously. When false (default), call connection:Fire(...) to run it immediately.
signalNameNoName of the RBXScriptSignal member on the instance (e.g. 'Touched', 'Changed'). Leave empty/omit if instancePath already evaluates to the signal.
instancePathYesLua expression resolving to the Instance that owns the signal (e.g. 'game.Workspace.Door'). 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.
connectionIndexNoZero-based index of the target connection within getconnections(signal), matching the Index reported by list-signal-connections. Defaults to 0 (the first connection).

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, readOnly=false, idempotent=false, but the description adds far more: client-side only (does not reach the server), pcall-guarded because Fire/Defer may be absent on foreign/C connections, dependency on getconnections with a defined degradation path ({ error }), and the exact return shape. This is rich behavioral context beyond the structured fields.

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-loads the critical 'MUTATES CLIENT STATE' warning and the core semantics in the first two sentences. It is longer than needed, with a duplicated inline signature plus phase/capability/verification boilerplate that partly repeats the schema, but the ordering keeps the important content first.

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?

For a 6-parameter mutating tool with no output schema, the description covers prerequisites, side effects, failure behavior, and the return object shape. 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 description coverage is 100%, so the schema already documents instancePath, signalName, connectionIndex, defer, args, and threadContext in detail. The description's inline signature restates those fields and adds the pointer to list-signal-connections, which the schema's connectionIndex description already contains. Baseline 3 applies 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?

Opens with a specific verb+resource and scope ('Invokes a single connection's :Fire(...)'), and explicitly distinguishes itself from the sibling fire-signal ('unlike fire-signal, which triggers every connection'). An agent can differentiate it without opening any 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?

Gives explicit when-to-use ('isolating and testing a single suspected handler'), names the alternative (fire-signal), and routes the agent to the prerequisites (list-signal-connections to find indices). Nothing is left 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