Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Call a method on a live Instance

invoke-method
Destructive

Call methods on live Roblox Instances by resolving a Luau path with typed arguments, returning the result; use for debugging or intentional game-state mutations.

Instructions

ACTS ON LIVE GAME STATE. Resolve a Luau expression to an Instance and call one of its methods as a colon-call (inst:Method(args...)), returning whatever the method returns. Useful while debugging for :Destroy(), :GetChildren(), :FindFirstChild(name), :Clone(), :GetAttribute(name), :SetAttribute(name, value), :WaitForChild(name), Humanoid:TakeDamage(n), Humanoid:MoveTo(pos), Tool:Activate(), etc. Each argument is a typed value; use kind='raw' for non-primitive arguments (Vector3, Enum, Instance, ...). The call is pcall-guarded. WARNING: many methods MUTATE the game (e.g. :Destroy(), :SetAttribute, :TakeDamage) and the effect is immediate and may replicate — only call methods you understand. Returns { Path, Method, ok, ReturnValues } or { error }. Signature: { instancePath: string, methodName: string, args: {{ kind: "string" | "number" | "boolean" | "nil" | "raw", value: string | number | boolean? }}?, threadContext: number? }. Phase: act; cost=medium; idempotency=contextual-write. Requires: active-client, resolved-target, explicit-mutation-approval. Produces: operation-receipt. Verify with: assert-state. Safety: MUTATING; executes caller-selected behavior in the live client. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoOrdered list of arguments passed to the method after `self`. Omit or pass [] for a no-argument call like :Destroy() or :GetChildren().
methodNameYesThe exact method name to call (case-sensitive), e.g. 'Destroy', 'GetChildren', 'FindFirstChild', 'Clone', 'GetAttribute', 'SetAttribute', 'TakeDamage'. Invoked as a colon-call so `self` is the instance.
instancePathYesLuau expression resolving to the Instance to call the method on, e.g. 'game.Workspace.Part', 'game.Players.LocalPlayer.Character.Humanoid', or 'game:GetService("Lighting")'. Evaluated as `return <instancePath>`.
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.4/5.0
Behavior5/5

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

Annotations already flag destructive/non-idempotent, and the description adds materially: the call is pcall-guarded, mutations are immediate and may replicate, explicit-mutation-approval/active-client/resolved-target are required, and it returns {Path, Method, ok, ReturnValues} or {error}. It also warns the agent to only call methods it understands.

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 crucial 'ACTS ON LIVE GAME STATE' and the mutation warning, and the example method list aids recognition. It is on the verbose side, with a trailing phase/cost/requires/produces/verify metadata block that partly duplicates annotations and adds length.

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 mutating live-state tool with no output schema, the description covers prerequisites, return shape, failure behavior, and the safety contract, and points to tool-schema for exact fields. An agent has everything needed to decide and invoke 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 documents kind, value, methodName, instancePath, and threadContext thoroughly. The description's signature recap and kind='raw' guidance largely restate what the schema says, adding only marginal meaning, so the baseline 3 is appropriate.

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+resource: resolve a Luau expression to an Instance and call one of its methods as a colon-call, returning the method's result. This clearly separates it from generic execution siblings like execute, run-luau, eval-expression, and closure-invocation tools such as invoke-closure.

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 strong context ('useful while debugging') and concrete example methods, plus the raw-kind rule for non-primitive args. It does not, however, route the agent to more specific siblings like destroy-instance, set-instance-property, or set-attribute, which cover some of the same mutations with tighter contracts.

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