Skip to main content
Glama

searchAndReplace

Destructive

Find and replace text or regex patterns across workspace files with support for capture groups, file glob filtering, and dry-run previews.

Instructions

Find and replace across workspace files. Supports regex with capture groups. Returns modified files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYesText or regex pattern to search for
replacementYesReplacement text. For regex mode, supports $1, $2, etc. capture group references.
globNoFile glob pattern to limit scope (e.g. '**/*.ts', 'src/**/*.py'). Omit to search all text files.
isRegexNoTreat pattern as a JavaScript regex. Default: false (literal string match).
caseSensitiveNoCase-sensitive match. Default: true.
dryRunNoPreview changes without writing files. Default: false.
includeIgnoredNoSearch inside .gitignored files (e.g. node_modules, build output). Default: false.
Behavior3/5

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

Annotations already provide destructiveHint: true; description adds that it returns modified files. No additional warnings or details on side effects.

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 that front-load the main action and return info. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks output format details (e.g., diff, file list). No output schema. For a destructive tool with 7 parameters, more completeness would help.

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 covers all parameters with full descriptions. Description mentions regex and capture groups, but this is redundant with 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 'Find and replace across workspace files' with specific verb+resource. Distinguishes from sibling tools like editText by emphasizing cross-file scope.

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?

No explicit guidance on when to use versus other tools like editText or replaceBlock. Does not mention when-not or alternatives.

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/Oolab-labs/patchwork-os'

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