Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_search

Search the open Studio place for instances by query and optional scope, so you can locate objects before inspecting or editing them.

Instructions

Search instances in the open Studio place.

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": {
      "query": "<query>"
    },
    "name": "roblox_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
scopeNogame

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about match semantics (name substring, class name, path), case sensitivity, result limits, or whether the search is read-only. Only 'in the open Studio place' hints at a runtime dependency on an active place. With an output schema present, return-shape explanation is not required, but search behavior itself is undisclosed.

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?

A single front-loaded sentence with no filler or redundancy. It is terse rather than bloated; the problem is omission, not wordiness.

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?

Output schema exists, so return values need not be described, but for a 2-parameter tool with zero schema documentation the definition leaves the agent unable to set 'scope' or predict match behavior. It is not complete enough to invoke confidently without opening the schema and guessing.

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% for both parameters, so the description must compensate and does not. 'query' is only obliquely implied by 'search', and 'scope' (default 'game') is never mentioned, leaving its valid values and effect entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

'Search instances in the open Studio place' gives a specific verb (search) and resource (instances) plus the scope of the target environment. It is clear on its own but never distinguishes itself from plausible siblings like roblox_grep, roblox_tree, or roblox_class, which an agent may reasonably consider for the same goal.

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?

The description states no conditions for when to use this versus alternatives, no prerequisites (does a place need to be open?), and no exclusions. The phrase 'in the open Studio place' is the only contextual hint, and it is implicit rather than a usage rule.

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