Skip to main content
Glama

tree

View a compact Roblox Studio instance hierarchy with class, name, tag, and path filters, listing matching instances and their disambiguated paths for quick inspection.

Instructions

Compact view of the instance hierarchy (Name [Class] (+N hidden children)). With class/name/tag filters, lists matching instances with full ~N-disambiguated paths. Faster and terser than search_game_tree.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoMax lines. Default 300.
tagNoOnly instances with this CollectionService tag.
nameNoOnly instances whose name contains this (case-insensitive).
pathNoStart instance, e.g. Workspace.Map (default: whole game).
classNoOnly instances where IsA(class), e.g. BasePart, BaseScript, GuiObject.
depthNoLevels to expand. Default 2 (10 with filters).
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.
script_infoNoAnnotate scripts with RunContext / Disabled state. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations present, the description does real work: it discloses the rendered output format, that hidden children are collapsed into a '+N' marker, and that paths in filtered mode are length-disambiguated rather than raw names. It omits two behavioral facts an agent would want — that output is line-capped (max, default 300) and what happens at that cap, and that this is a purely read-only inspection.

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?

Two sentences, both load-bearing, with the core identity stated first and the competitive comparison last. No restating of the parameter list, no filler; the '+N hidden children' example is arguably the single most useful string in the definition.

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?

For a read-only, nine-parameter inspection tool with no output schema, this covers what matters: what is returned, how filters change the return shape, and how it relates to the search alternative. The remaining gaps (line-cap behavior) are minor and partially covered by the max parameter's own schema description.

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 nine parameters (max, tag, name, path, class, depth, studio, context, script_info) are already documented in the schema. The description reinforces that class/name/tag act as filters and that they also change the depth default, but adds no syntax or format detail beyond the schema, so the baseline of 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?

It names both the resource (instance hierarchy) and the two concrete behaviors: a compact tree render with the literal output shape 'Name [Class] (+N hidden children)', and a filtered mode that lists matches as full disambiguated paths. It explicitly separates itself from search_game_tree, so an agent can pick between them without opening either 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?

It gives a clear context for selection by stating it is 'faster and terser than search_game_tree' and by explaining that adding class/name/tag filters switches the output from a tree to a flat list of matching paths. It stops short of stating when not to use it (e.g., when full untruncated names or deep expansion are required, use the sibling instead).

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