Skip to main content
Glama

search_objects

Read-only

Finds Roblox instances by name, class, or both under a root path and lists their paths for read-only inspection; narrow the search when the 200-result cap is hit.

Instructions

Find instances by name, class or both under a root and list their paths. Read-only; stops at 200 results and says so, so narrow the search when that happens. Use matchMode exact or wholeWord to cut the noise of substring matches. To match a property value (every part with Material=Wood) use search_by_property; to search the Roblox marketplace use search_assets.

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

Input Schema

NameRequiredDescriptionDefault
nameNoText to match against instance names. Omit to match any name (then give className).
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
rootPathNoWhere to start searching. 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)". Omit to use the whole DataModel (game).
classNameNoOnly match this class or classes that inherit from it, e.g. "Model" or "GuiObject".
matchModeNoHow name is matched. regex uses Lua patterns. Default substring.
caseSensitiveNoMatch name case-sensitively. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • changedInput schema / properties / caseSensitive / description
      Previous value: -"default false"New value: +"Match name case-sensitively. Default false."
    • addedInput schema / properties / className / description
      Added value: +"Only match this class or classes that inherit from it, e.g. \"Model\" or \"GuiObject\"."
    • changedInput schema / properties / matchMode / description
      Previous value: -"name match mode (default substring)"New value: +"How name is matched. regex uses Lua patterns. Default substring."
    • addedInput schema / properties / name / description
      Added value: +"Text to match against instance names. Omit to match any name (then give className)."
    • addedInput schema / properties / rootPath / description
      Added value: +"Where to start searching. 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)\". Omit to use the whole DataModel (game)."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The readOnlyHint annotation already declares the safe-read profile, so the 'Read-only' sentence adds little, but the description contributes real behavior the annotations do not: a hard 200-result truncation that announces itself and advice to narrow scope when it triggers. It does not describe ordering of results, which is a minor omission for a list tool.

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?

Three tight sentences with the core behavior front-loaded, followed by the cap caveat and then the routing exclusions. No filler and no repetition of schema text.

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?

With no output schema, the description still tells the agent what comes back (instance paths) and how the result set is bounded. All six parameters are schema-documented, and the sibling delegation covers the main ambiguity for a search tool.

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 100% so the baseline is 3, and the description goes slightly beyond it by giving operational semantics for matchMode ('exact or wholeWord to cut the noise of substring matches') and tying name/className/rootPath into the search story. It stops short of clarifying place, caseSensitive, or regex behavior, so it is good but not fully additive.

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?

States a specific verb-plus-resource ('Find instances by name, class or both under a root and list their paths') and names what it is not: search_by_property for property values and search_assets for the marketplace. An agent can route correctly without opening the 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 when-to-use guidance: narrow the search when the 200-result cap is hit, use matchMode exact or wholeWord to reduce substring noise, and delegate to named siblings for property-value and marketplace searches. Alternatives and exclusion conditions are both spelled out.

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