Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_tree

Displays the project structure and file tree of a Roblox place, letting you map instances and scripts before editing or inspecting the hierarchy.

Instructions

Project structure / file 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": "roblox_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNogame

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and does not state that this is a read-only operation, how deep the tree is, or whether it operates on the whole game or a subtree. The existence of an output schema reduces the need to explain return values, but key behavioral traits remain undisclosed.

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

Conciseness3/5

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

The description is very short and front-loaded, with no wasted sentences. However, the slash-separated fragment is under-specified rather than genuinely concise, and it does not establish a clear action.

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?

For a tree-inspection tool with one optional parameter and no annotations, the definition should clarify path semantics and scope. The output schema can cover return values, but the description does not provide enough context to invoke the tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the single path parameter, but it adds no meaning beyond the parameter name. An agent can infer that path may be the tree root, but the description does not clarify accepted path formats, default behavior, or scope.

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 identifies the resource as a project structure or file tree, which is more specific than the tool name alone. However, it omits an explicit verb and does not clarify whether it retrieves, renders, or summarizes the tree, leaving the exact operation vague.

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 guidance on when to use this tool or how it relates to siblings such as roblox_search, roblox_read, or roblox_class. The description gives no exclusions, prerequisites, or alternative-selection criteria.

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