Skip to main content
Glama

get_descendants

Read-only

List every descendant of a Roblox instance, one line each with class and full path down to a depth limit. Read-only; returns exact paths you can pass to other tools.

Instructions

List every descendant of an instance, one line each with its class and full path, down to a depth limit. Read-only. Gives exact paths you can pass to other tools, but nothing is folded, so it gets long on big models: prefer get_tree to map a large area, and describe for one instance in detail.

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": "get_descendants"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesInstance whose descendants to list. Dot path from the DataModel root, e.g. "Workspace.Map.Door" or "StarterGui.HUD.Frame". A leading "game." is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. "Part (2)".
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
maxDepthNoHow many levels below path to include. Default 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / maxDepth / description
      Added value: +"How many levels below path to include. Default 5."
    • addedInput schema / properties / maxDepth / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / maxDepth / minimum
      Added value: +1
    • changedInput schema / properties / maxDepth / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / path / description
      Added value: +"Instance whose descendants to list. Dot path from the DataModel root, e.g. \"Workspace.Map.Door\" or \"StarterGui.HUD.Frame\". A leading \"game.\" is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. \"Part (2)\"."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so 'Read-only' is redundant. The description earns credit beyond that by disclosing output volume behavior ('nothing is folded, so it gets long on big models') and that returned paths are directly reusable in other tools. It does not cover pagination or truncation at very large depths, which keeps it off a 5.

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?

Front-loaded with the core action, then output format, then routing guidance. Dense but every clause carries information; the 'Read-only' fragment slightly duplicates the annotation.

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 exists, but the description specifies the return shape (one line per descendant with class and full path) and warns about size, which is the key completeness gap for a list tool. Combined with full schema coverage and annotations, nothing essential is missing.

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 the schema already documents path, place, and maxDepth in detail. The description only echoes the depth limit ('down to a depth limit') and adds no syntax or default nuance beyond the schema. Baseline 3 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?

Specific verb and resource plus the exact output shape: 'List every descendant of an instance, one line each with its class and full path.' It also differentiates itself from get_tree and describe by name, so an agent can choose without opening another schema.

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?

Explicit routing with conditions: use get_tree to map a large area, describe for one instance in detail, and this tool when you need exact paths to pass to other tools. Both alternatives and the selection criteria are stated.

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