Skip to main content
Glama

query_instances

Query Roblox instances in the game hierarchy. Retrieve objects by path, class, name, property, or tag, and explore their children, descendants, and structure.

Instructions

Query instances in the Roblox place. Prefer a typed action over execute_luau. Actions: get, children, descendants, ancestors, find_child, find_descendant, wait_for_child, search_class, search_name, search_property, search_tag, class_info, file_tree (nested outline), project_structure (service/script counts). Paths: 'game.Workspace.Model.Part' or 'Workspace/Model/Part'. Prefer rbId (from a prior summary) over path when both are set — names like Part are not unique. Aliases: childName/descendantName/query→name, root→path, propertyName→property, id→rbId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAlias for rbId
tagNoTag for search_tag
nameNoChild/descendant name or name substring for searches
pathNoInstance path. Defaults to game. Alias: root. An RBId GUID is also accepted.
rbIdNoRoBridge instance id from a prior summary. Preferred over path when both are set. Alias: id
rootNoAlias for path
depthNoAlias for maxDepth
queryNoAlias for name (search_name)
valueNoOptional property value to match (search_property)
actionYes
timeoutNoSeconds to wait (wait_for_child, default 5, max 30)
maxDepthNoMax depth for file_tree (default 5) / project_structure (default 3)
propertyNoProperty name for search_property
childNameNoAlias for name (find_child / wait_for_child)
classNameNoClassName for search_class / class_info
maxResultsNoMax results for searches/descendants (default 100)
includePropsNoInclude common properties in results
propertyNameNoAlias for property
propertyValueNoAlias for value
descendantNameNoAlias for name (find_descendant)
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explains path formats, aliases, and the rationale for rbId preference, but does not explicitly confirm the tool is read-only or describe result formatting/performance implications.

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?

The description is long but densely packed with necessary information for a tool with 20 parameters: action list, path syntax, alias map, and usage preference. It is front-loaded with the core purpose and avoids fluff.

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?

Given the tool's complexity (20 params, no output schema), the description covers actions, path formats, aliases, defaults, and usage guidance. It lacks examples but is otherwise comprehensive enough for an agent to select and invoke correctly.

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 95%, so baseline is 3. The description adds valuable context beyond the schema by explaining alias relationships and the rbId-over-path preference, which clarifies parameter usage.

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 states 'Query instances in the Roblox place' and lists 14 specific actions, making the tool's function clear and specific. It distinguishes itself from sibling tools like execute_luau and spatial_query.

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?

Explicitly instructs 'Prefer a typed action over execute_luau' and provides guidance on using rbId over path because 'names like Part are not unique.' However, it does not detail when to use this tool versus spatial_query or manage_properties.

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/Allusia1/RoBridge'

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