Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create a Drawing object (ESP/debug overlay)

draw-create
Destructive

Creates persistent on-screen Drawing overlay objects in Roblox executors, applying properties for ESP boxes, tracers, and HUDs, and returns an ID for updates or removal.

Instructions

Creates a new on-screen overlay object via the executor Drawing library (used for ESP boxes, tracers, name tags, and debug HUDs) and registers it so it survives across tool calls. Calls Drawing.new(type) for type in {Line, Text, Circle, Square, Quad, Triangle, Image}, applies the given properties, stores the handle in getgenv().__mcp_drawings under a new integer id, and returns { id, type } — pass that id to draw-update / draw-remove. PROPERTIES: each property value is a Luau EXPRESSION STRING evaluated via loadstring, so rich types work: Color = 'Color3.new(1,0,0)', From = 'Vector2.new(10,10)', To = 'Vector2.new(200,200)', Position = 'Vector2.new(100,100)', Visible = 'true', Thickness = '2', Text = '"hello"', Size = '18'. Common props: Visible(bool), Color(Color3), Transparency(number 0..1), ZIndex(number). Per type — Line: From, To, Thickness; Text: Text, Size, Position, Center, Outline; Circle: Center, Radius, NumSides, Thickness, Filled; Square: Size, Position, Thickness, Filled. Requires the Drawing table (type-guarded); on an executor without it, it returns { error = "Drawing is not available in this executor." }. Every call is pcall-guarded. Returns { id, type, applied[] } or { error }. Signature: { type: "Line" | "Text" | "Circle" | "Square" | "Quad" | "Triangle" | "Image", properties: any?, threadContext: number?, timeoutMs: number? }. Phase: act; cost=medium; idempotency=contextual-write. Requires: active-client, explicit-mutation-approval. Capabilities: Drawing. Produces: created-handle. Verify with: list-drawings. Safety: MUTATING; changes executor drawing overlay state. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesThe Drawing object type to create via Drawing.new(type): one of Line, Text, Circle, Square, Quad, Triangle, Image.
timeoutMsNoOptional per-call deadline in milliseconds; omit it to use the tool or server default.
propertiesNoMap of property name -> Luau expression STRING to assign after creation. Values are evaluated via loadstring, so use Luau syntax: Color = 'Color3.new(1,0,0)', From = 'Vector2.new(10,10)', Visible = 'true', Thickness = '2', Text = '"label"'. Unknown/failed properties are reported in 'applied' with ok=false but do not abort the create.
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.5/5.0
Behavior5/5

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

Annotations already declare the mutation profile (destructiveHint=true, idempotentHint=false), and the description goes well beyond them: type-guard on the `Drawing` table, the exact error payload when unavailable, pcall-guarding on every call, the fact that handles persist across tool calls, and that failed properties appear in `applied` with ok=false without aborting the create.

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?

The opening sentence is well front-loaded and dense with useful detail, but the body is a very long single block that re-lists the full signature already present in the schema and appends machine metadata (Phase, cost, Capabilities, Produces, Safety) as one run-on string. Several clauses restate structured data rather than adding new information.

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 carries the return contract itself ({ id, type, applied[] } vs { error }) and covers failure modes, persistence, and executor availability. For a mutating 4-parameter tool this is complete enough that an agent could invoke it correctly without opening the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning the schema lacks: the loadstring/Luau-expression-string convention for `properties` and per-type supported properties (Line: From/To/Thickness; Text: Text/Size/Position/Center/Outline; Circle: Center/Radius/NumSides/Thickness/Filled). It adds value beyond the schema without fully enumerating Quad/Triangle/Image props.

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 and resource ('creates a new on-screen overlay object via the executor `Drawing` library') and enumerates exactly what it produces (handle stored in getgenv().__mcp_drawings, returns { id, type }). It is unmistakably distinct from the sibling draw-update / draw-remove / draw-clear / list-drawings tools.

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?

Explicitly routes the agent downstream ('pass that id to draw-update / draw-remove') and names the verification step ('Verify with: list-drawings'), plus states prerequisites (active-client, explicit-mutation-approval). It does not describe when not to use it or when a non-Drawing overlay approach would be preferable, so it stops short of full 5-level guidance.

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