Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update properties of an existing Drawing object

draw-update
Destructive

Update an existing Drawing overlay by integer id: move tracers, recolor ESP boxes, toggle visibility, or change labels via Luau property expressions.

Instructions

Mutates a Drawing overlay previously created by draw-create, looking the handle up by its integer id in getgenv().__mcp_drawings and assigning each given property. Use it to move a tracer (To = 'Vector2.new(400,300)'), recolor an ESP box (Color = 'Color3.new(0,1,0)'), toggle visibility (Visible = 'false'), or change a label (Text = '"BOSS"'). PROPERTIES: each value is a Luau EXPRESSION STRING evaluated via loadstring, identical to draw-create. Unknown/failed properties are reported per-property in 'updated' (ok=false) without aborting the rest. Requires the Drawing table (type-guarded). If the id is unknown it returns { error }; on an executor without it, it returns { error = "Drawing is not available in this executor." }. Returns { id, updated[] } or { error }. Signature: { id: number, properties: {[string]: any}, threadContext: number?, timeoutMs: number? }. Phase: act; cost=medium; idempotency=contextual-write. Requires: active-client, explicit-mutation-approval. Capabilities: Drawing. Produces: structured-result. 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
idYesInteger id of the Drawing object (as returned by draw-create / list-drawings).
timeoutMsNoOptional per-call deadline in milliseconds; omit it to use the tool or server default.
propertiesYesMap of property name -> Luau expression STRING to assign. Values are evaluated via loadstring, so use Luau syntax: Color = 'Color3.new(0,1,0)', To = 'Vector2.new(400,300)', Visible = 'false', Text = '"label"'. Failed properties are reported in 'updated' with ok=false.
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/readOnly/idempotent hints, and the description adds substantial context on top: per-property failure isolation (ok=false without aborting), the exact { error } shapes for unknown id and missing Drawing executor, the loadstring evaluation model, and the phase/cost/idempotency classification. This is well beyond what structured fields 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 purpose and lookup mechanism are front-loaded and the examples are efficient. However the tail is loaded with meta-boilerplate ('Phase: act; cost=medium; idempotency=contextual-write...') and a generic 'inspect tool-schema' instruction that do not earn their space in a description.

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 compensates by specifying the return shape ({ id, updated[] } or { error }) and the failure modes. For a nested-object mutation tool with a type-guarded dependency, the description covers everything an agent needs to call it correctly.

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; the description nonetheless adds real meaning by stressing that property values are Luau EXPRESSION STRINGS evaluated via loadstring and by listing worked examples (Color = 'Color3.new(0,1,0)'). It also restates the signature, which is minor redundancy but not harmful.

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 ('Mutates a Drawing overlay previously created by draw-create') and names the lookup mechanism (getgenv().__mcp_drawings by integer id). The sibling contrast with draw-create is explicit, so an agent can distinguish this from create/list/remove drawing tools 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 Guidelines4/5

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

Gives concrete usage contexts — moving a tracer, recoloring an ESP box, toggling visibility, changing a label — and names prerequisites (must be created by draw-create) and a verification sibling (list-drawings). It never states when NOT to use it or which alternative to pick for bulk/instance property changes, so it falls short of a 5.

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