Skip to main content
Glama
RealSlimShady2000

Roblox Executor MCP Server

Grep across all scripts in the game

script-grep

Search decompiled Roblox scripts using JavaScript regex or literal string matching to find exact identifiers or code patterns.

Instructions

Search decompiled Roblox scripts with JavaScript regex or literal string matching. Use for exact identifiers or code patterns; use semantic-search-scripts when behavior is known but names are not.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of scripts to return results from (default: 50)
queryYesThe search pattern. Supports JavaScript RegExp syntax: \d, \w, \s, \b, character classes [a-z], alternation (foo|bar), quantifiers (+, *, ?), groups, lookaheads, etc. Use the literal flag for exact string matching.
literalNoWhen true, treats the query as a plain literal string - no regex interpretation. Equivalent to grep -F / ripgrep -F. (default: false)
maxResultsNoMaximum total number of matches across ALL scripts (default: unlimited). Use this to cap total matches, e.g. maxResults=1 to find just the first match.
contextLinesNoNumber of lines of context to show before and after each match (default: 2)
caseSensitiveNoWhen false, matches case-insensitively. Equivalent to grep -i. (default: true)
maxMatchesPerScriptNoMaximum number of matches to return per script (default: 20)
Behavior2/5

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

No annotations provided; description does not disclose whether the tool is read-only, performance implications, or any side effects. Missing behavioral context beyond the basic search functionality.

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?

Two concise sentences with no unnecessary words. Efficiently communicates core functionality and usage distinction.

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?

No output schema and description does not mention what the results look like (e.g., list of scripts, match details, pagination). For a tool with 7 parameters, this is a notable omission.

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 coverage is 100%, so parameters are well-documented in schema. Description adds some extra context (e.g., literal flag use) but does not significantly improve understanding beyond the schema.

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?

Clearly states it searches decompiled Roblox scripts with regex or literal matching, and distinguishes from sibling tool semantic-search-scripts by specifying when to use each.

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?

Explicitly tells when to use this tool (exact identifiers or code patterns) vs. semantic-search-scripts (when behavior is known but names are not).

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/RealSlimShady2000/exploitMCP420Edition'

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