Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List custom attributes used under a root

list-attributes
Read-onlyIdempotent

Scan instance descendants to collect custom attribute names, value types, samples, and counts, helping you discover attribute keys stored in a place without grepping scripts.

Instructions

Walk the descendants of a root instance and collect every unique custom attribute name (via GetAttributes()), with its observed value type, a sample value, and how many instances carry it. Use this when debugging gameplay data that is stored as instance attributes (e.g. QuestId, Health, OwnerUserId) and you want to discover which attribute keys exist in a place without grepping scripts. Returns [{ Name, ValueType, SampleValue, InstanceCount }] sorted by frequency. Work is capped at limit instances scanned. Signature: { root: any?, limit: any?, threadContext: number? }. Phase: observe; cost=medium; idempotency=read-only. Requires: active-client. Produces: bounded-candidates. Safety: read-only. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoDotted root path to scan descendants of (e.g. 'game.Workspace', 'game.ReplicatedStorage'). Defaults to 'game' (the whole DataModel). Narrow this to keep scans fast on large places.game
limitNoMaximum number of instances to scan before stopping (default: 1000). Lower this for a quick sample; raise it for exhaustive coverage at the cost of speed.
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.2/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/destructive, but the description adds real behavioral context: work is capped at `limit` instances scanned, cost=medium, and it 'Requires: active-client'. Some tags (Safety: read-only, idempotency=read-only) merely restate annotations.

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?

Core purpose and scope are front-loaded, and the return shape is stated compactly. The trailing metadata block (Phase/cost/idempotency/Safety/On failure) is verbose and partly redundant, but each clause carries some 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?

No output schema, but the description supplies the return shape [{ Name, ValueType, SampleValue, InstanceCount }], sort order, scan cap, prerequisites, and failure guidance. Everything needed to call it correctly is present.

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 all three parameters (root, limit, threadContext) are already documented with defaults and constraints. The description repeats the signature but adds no format or semantics beyond the schema, so baseline 3 applies.

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 ('walk the descendants of a root instance and collect every unique custom attribute name') plus the returned fields. An agent can distinguish this from set-attribute or get-instance-properties without opening the schema.

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 a clear when-to-use ('debugging gameplay data stored as instance attributes... discover which attribute keys exist without grepping scripts') and implies the alternative is script grep. No explicit when-not or named sibling alternative, so it stops 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