Skip to main content
Glama
EL4CTEO

Roblox Studio MCP

Inspect instances

inspect
Read-onlyIdempotent

Reads properties, attributes, tags, and children of Roblox instances in batches, returning valid data even if some paths are invalid.

Instructions

Reads properties, attributes, tags and children of one or more instances. Pass every path you care about in a single call — batching costs one round trip instead of N.

Property selection comes from the live Roblox API dump for each instance's actual class, so it stays correct across engine updates: concise — class and child count only standard — the properties that characterise the class (Part gets Size, Position, CFrame, Anchored, Material...) full — every readable property; expensive, use on one or two instances at most

Bad paths do not fail the call: they come back under failures while the valid ones still return, so one typo does not cost you the whole batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsYesInstance paths, e.g. ["Workspace.Baseplate", "Lighting"].
detailNoHow much to return per item. 'concise' = name + class only, cheapest, use when scanning or counting. 'standard' = the properties that matter for most edits. 'full' = every readable property, expensive — use only after you have narrowed to a handful of instances.standard
studioIdNoTarget Studio; omit for the active one.
propertiesNoRead exactly these properties instead of the detail-level default. Use when you want one specific value across many instances.
includeChildrenNoInclude a name/class listing of direct children.
Behavior5/5

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

Beyond the readOnly/idempotent/no-destructive annotations, the description discloses failure isolation (bad paths return under failures), live Roblox API property selection, and the relative cost of detail levels. This materially improves agent prediction of side effects and outcomes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The action and top-level batch advice come first, then detail options in scannable bullets, then edge-case behavior. Each sentence adds a distinct fact and the length is proportionate to the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers failure handling, cost of detail levels, and property freshness, and annotations cover safety. It does not spell out the exact success-response shape (e.g., per-path objects), and there is no output schema, which leaves a minor inference gap for agents.

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 high (100%), but the description enriches the detail and properties parameters with concrete mode semantics (class/child count, characterizing properties, expensive full mode) and explains batching intent. It doesn't add much beyond schema for paths/studioId/includeChildren, so a modest premium over baseline 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?

The description opens with 'Reads properties, attributes, tags and children of one or more instances', a specific read verb plus a concrete resource. The wording clearly separates this inspect operation from mutation siblings, so an agent can identify the tool's role even before reading schema details.

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?

It gives strong operational guidance: batch all desired paths into one call, choose detail level by need, and reserve full mode for one or two instances. It does not explicitly mention sibling alternatives like tree/find for when to choose them instead, so it stops short of full alternative routing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EL4CTEO/rbx-studio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server