Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_grep

Search script sources across a Roblox place to locate patterns and matching code. Use it to find where identifiers, strings, or logic appear before editing Luau scripts.

Instructions

Grep script sources across the 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": {
      "pattern": "<pattern>"
    },
    "name": "roblox_grep"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
patternYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: read-only nature is only implicit in "grep", and there is no mention of rate limits, whether matches span multiple scripts, whether surrounding context lines are returned, or any side effects. An output schema exists, so return values need less explanation, but the operational profile remains opaque.

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?

It is a single short, front-loaded sentence with no waste, but here terseness crosses into under-specification rather than efficiency, since nothing about scoping or result shape is conveyed.

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 tool with a 0%-documented two-parameter schema and no annotations, the description does far too little; the output schema covers return values, but pattern syntax, limit semantics, and search scope/behavior are all missing.

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%, and the description does not explain either parameter. The word "grep" hints that `pattern` is a pattern rather than a literal string, but neither the pattern syntax/flavor nor the meaning or default behavior of `limit` is stated, so half the parameters are undocumented everywhere.

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?

"Grep script sources across the place" gives a specific verb (grep) and resource (script sources) plus scope (whole place), which is more precise than a generic search tool. It doesn't explicitly contrast with siblings like roblox_script_get or roblox_search, but the pattern-matching framing is distinctive enough for an agent to pick it apart from a single-script read.

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 versus roblox_search, roblox_read, or roblox_script_get, no mention of prerequisites such as the place/session being loaded, and no note on when results might be truncated. The agent must infer usage entirely.

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