Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Inspect a single signal connection in detail

get-connection-info
Read-onlyIdempotent

Return full metadata for one connection on an RBXScriptSignal by zero-based index, including handler source and thread status, to inspect a specific listener.

Instructions

Return the full Connection metadata for ONE connection on an RBXScriptSignal, selected by zero-based index. Reports Index, Enabled, LuaConnection, ForeignState, whether it has a Function/Thread, the connected thread's status (when present), and — for Lua connections — the handler function's Source script, Name, LineDefined, NumParams, IsVararg and What. Use this to zoom in on a specific listener after list-signal-connections shows you the index of interest. Requires getconnections; degrades with a clear { error } if unavailable or if the index is out of range. Returns { Signal, Instance?, ConnectionCount, Connection: {...} }. Signature: { instancePath: string, signalName: any?, connectionIndex: any?, threadContext: number? }. Phase: observe; cost=medium; idempotency=read-only. Requires: active-client, resolved-target. Capabilities: getconnections. Produces: structured-observation, created-handle. Safety: read-only. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signalNameNoName of the RBXScriptSignal member on the instance (e.g. 'Touched', 'Changed', 'OnClientEvent'). 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 RBXScriptSignal itself.
threadContextNoOptional Roblox thread identity for this call; omit it to use the server default.
connectionIndexNoZero-based index of the connection to inspect, as reported by list-signal-connections. 0 is the first connection. Must be < ConnectionCount or a clear { error } is returned.

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 readOnly/idempotent/no-open-world, and the description still adds real behavioral context: it requires getconnections, degrades with a clear { error } when unavailable or the index is out of range, and enumerates the returned fields and their conditions (e.g. thread status only when present).

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 purpose, then usage, failure behavior, and return shape before the structured metadata tail. The signature/phase/cost block is somewhat boilerplate-heavy but each line is informative; nothing is truly wasteful.

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 fully documents the return shape ({ Signal, Instance?, ConnectionCount, Connection: {...} }) and enumerates the nested fields. It also covers failure modes and prerequisites, so an agent has everything needed to call it correctly.

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 carries parameter meaning; the description's 'Signature' line merely restates the four parameters and adds no syntax or format detail beyond the schema. Baseline 3 is correct 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?

The description opens with a specific verb+resource+scope: 'Return the full Connection metadata for ONE connection on an RBXScriptSignal, selected by zero-based index.' It explicitly contrasts with the sibling list-signal-connections (bulk listing vs. single-connection zoom), so an agent can distinguish them without opening schemas.

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?

States exactly when to use it ('after list-signal-connections shows you the index of interest') and names the alternative tool. Prerequisites (getconnections) and the out-of-range/unavailable conditions are also documented, 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