Skip to main content
Glama
xixfaces

Roblox Executor MCP

by xixfaces

Grep across all scripts in the game

script-grep

Search decompiled Roblox scripts using regex or literal strings to find code patterns or exact identifiers.

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
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.
limitNoMaximum number of scripts to return results from (default: 50)
contextLinesNoNumber of lines of context to show before and after each match (default: 2)
maxMatchesPerScriptNoMaximum number of matches to return per script (default: 20)
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.
literalNoWhen true, treats the query as a plain literal string - no regex interpretation. Equivalent to grep -F / ripgrep -F. (default: false)
caseSensitiveNoWhen false, matches case-insensitively. Equivalent to grep -i. (default: true)
Behavior3/5

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

No annotations are provided, so the description carries the full burden of disclosing behavioral characteristics. It implies a read-only search operation but does not explicitly state that it does not modify scripts or require special permissions. More detail on side effects or constraints would improve transparency.

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?

The description is extremely concise: two sentences that front-load the core purpose and usage comparison. Every word adds value with no redundancy or filler.

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?

Given that there are 7 well-documented parameters and no output schema, the description provides adequate context for a grep-like tool. It could be improved by mentioning the return format or limitations (e.g., only searches decompiled scripts), but it is still sufficiently complete for effective tool selection.

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?

The input schema has 100% description coverage, so the baseline is 3. The tool description does not add additional meaning beyond what the schema already provides for parameters. It focuses on usage context rather than parameter details.

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 clearly states the tool's purpose: searching decompiled Roblox scripts with JavaScript regex or literal string matching. It also distinguishes from the sibling tool 'semantic-search-scripts' by specifying use cases (exact identifiers or code patterns vs. behavior known but names not).

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?

The description explicitly tells when to use this tool (exact identifiers or code patterns) and when to use the alternative 'semantic-search-scripts' (behavior known but names not). This provides clear decision guidance for the agent.

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/xixfaces/roblox-executor-mcp'

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