Skip to main content
Glama
EL4CTEO

Roblox Studio MCP

What a class can do

api
Read-onlyIdempotent

Retrieve properties, methods, and events for any Roblox class from the running engine, ensuring accurate Luau code before you write it.

Instructions

Lists the properties, methods and events of any Roblox class, read from the engine that is running.

Use it before writing Luau against a class you are not certain of. Guessing a method name costs a runtime error and a round trip; this costs one call and is never out of date, because the answer comes from the running binary rather than from a published dump or from training data. That matters most for exactly the classes worth checking — new ones, and ones that changed recently.

Members come back as signatures rather than bare names — AddAccessory(accessory: Instance), HoldDuration: number — because a name tells you something exists and a signature tells you how to call it, which is the actual question.

describe takes a class name and gives the members it declares itself, counting the inherited ones separately. classes searches class names, which is how to find one whose exact spelling you do not have.

Deprecated members are never listed, only counted — Instance has eight, including clone, remove and getChildren. They still run, so picking one from a list gives you working code and a deprecation warning in the user's output. Members no script may use at all are counted with them.

This is not the same as inspect. inspect reads the values on an instance that exists; this reads the shape of a class whether or not anything in the place is one — which is what you need when deciding what to create in the first place.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opNo'describe' details one class, 'classes' searches class names.describe
includeNodescribe only: which member kinds to return. Defaults to all three; narrow it when you only need one and the class is large.
containsNoclasses only: substring to match, case-insensitive, e.g. "constraint" or "gui". Omit to list everything.
studioIdNoTarget Studio; omit for the active one.
classNameNodescribe only: the class, e.g. "TweenService", "ProximityPrompt", "Humanoid". Case-sensitive.
inheritedNodescribe only: include members inherited from Instance and Object. Off by default because they swamp the answer — ProximityPrompt has 2 methods of its own and 42 inherited, and the two you want are not the ones you already know. The inherited count is reported either way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, and the description adds valuable behavior beyond that: results come from the running binary, members are returned as signatures, deprecated members are only counted and never listed, and deprecated members still execute with warnings. This is non-obvious, important behavioral context that is fully consistent with the 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?

The description is front-loaded with purpose and every paragraph carries a distinct, useful point. It is longer than a minimal definition, but the length is warranted by the need to explain deprecation semantics, signature format, and sibling differentiation, so there is no wasted text.

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 takes on the burden of explaining what the agent will receive: member signatures, inherited counts, and the fact that deprecated members are counted but not listed. It also covers both operations and their typical usage, making it complete for an introspection tool.

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 description coverage is 100%, so each parameter already has a meaningful description, giving a baseline of 3. The tool description adds genuine value by explaining the semantic difference between describe and classes and by justifying why inherited defaults to false, complementing rather than merely repeating the schema.

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 pair: 'Lists the properties, methods and events of any Roblox class, read from the engine that is running.' It explicitly contrasts with the sibling inspect, which reads values on an existing instance, so the agent can differentiate the two tools without inspecting 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?

It explicitly states when to use the tool: 'Use it before writing Luau against a class you are not certain of.' It also explains when not to use it, drawing a clear line against inspect, and gives guidance for choosing between the describe and classes operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.