Skip to main content
Glama

inspect

Retrieve an instance's properties, attributes, CollectionService tags, and child summary in Roblox Studio, with path disambiguation for dots, duplicate names, and playtest datamodels.

Instructions

Properties, attributes, CollectionService tags, and children summary of an instance (supports ~N disambiguation, dots in names, and playtest datamodels).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
propsNoOnly return these properties.
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.
contextNoDatamodel to run in. Default: edit when not playing, otherwise server.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it never states that this is a read-only operation, how ambiguous paths are reported, or how large the returned summary may be. It does add useful behavior context by disclosing playtest datamodel support and ~N disambiguation, which keeps it above a 1.

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?

A single tight sentence with no filler, and the returned data is front-loaded. The fragmentary grammar slightly reduces clarity, but nothing is wasted.

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

Completeness2/5

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

Four parameters, no annotations, and no output schema mean the description should explain the return shape and safety profile, but it does not. It also omits any explanation of the 'studio' parameter, which matters when multiple Studios are open.

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 coverage is 75%, so the baseline is 3. The description genuinely adds meaning for the undocumented 'path' parameter by explaining ~N disambiguation and dots in names, and it hints at the 'context' parameter via 'playtest datamodels', but it says nothing about 'props' or 'studio' beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (an instance) and enumerates what is returned: properties, attributes, CollectionService tags, and a children summary. However, it is a noun-phrase fragment with no verb, and it never distinguishes itself from plausible siblings such as 'instance' or 'tree', which an agent could easily mistake for the same read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The parenthetical mentions capabilities (~N disambiguation, dotted names, playtest datamodels) but these are feature notes, not selection guidance.

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