Skip to main content
Glama

script_grep

Search Roblox Studio scripts for substrings or /regex/ and return matching paths, line numbers, and lines; limit results and scope searches to specific instance paths.

Instructions

Search across all scripts in Studio (or under paths) for a substring or /regex/. Returns ~N-safe paths, line numbers, and matching lines.

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

Input Schema

NameRequiredDescriptionDefault
maxNoMax matches returned. Default 100.
pathsNoOnly search scripts under these instance paths.
queryYesSubstring or /regex/flags.
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. It does disclose the return shape and match limits, and the operation is clearly a read, but it says nothing about preconditions (must a Studio be connected?), scope limits (loaded vs. saved scripts), or performance on large codebases. Adequate but with clear gaps.

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?

A single front-loaded sentence covering scope, query forms, and return values with no filler. Every clause earns its place.

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?

For a four-parameter search tool with full schema coverage and no output schema, the description gives enough to call it correctly, including the returned fields. Minor incompleteness remains around when to use it instead of script_read and what happens with no active Studio.

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 all four parameters (query, paths, max, studio) are already documented in the schema. The description echoes the query form and path scoping but adds no syntax examples, regex flag behavior, or path format detail beyond what the schema states. Baseline 3 is correct.

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 names a specific verb and resource ('Search across all scripts in Studio') and adds scope qualifiers ('or under `paths`', 'substring or /regex/'), which is enough to distinguish it from single-script siblings like script_read or script_edit. It also states the return payload (paths, line numbers, matching lines), so an agent knows exactly what comes back.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the multi-file search tool versus script_read for whole-file reads, but the description never says when to prefer it or when not to. The only conditional guidance ('only needed when several Studios are open') lives in the schema for the `studio` param, not in the description.

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