Skip to main content
Glama
shk1447

ripgrep-mcp

by shk1447

advanced-search

Perform advanced text searches across files using ripgrep with customizable options such as case sensitivity, file type filters, and context lines. Supports regex or literal patterns.

Instructions

Advanced search with ripgrep with more options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYesThe search pattern (regex by default)
pathYesDirectory or file(s) to search.
caseSensitiveNoUse case sensitive search (default: auto)
fixedStringsNoTreat pattern as a literal string, not a regex
filePatternNoFilter by file type or glob
fileTypeNoFilter by file type (e.g., js, py)
maxResultsNoLimit the number of matching lines
contextNoShow N lines before and after each match
invertMatchNoShow lines that don't match the pattern
wordMatchNoOnly show matches surrounded by word boundaries
includeHiddenNoSearch in hidden files and directories
followSymlinksNoFollow symbolic links
showFilenamesOnlyNoOnly show filenames of matches, not content
showLineNumbersNoShow line numbers
useColorsNoUse colors in output (default: false)
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It mentions ripgrep but does not reveal important traits like performance impact, default behaviors (e.g., case sensitivity auto), or side effects. This is insufficient for a tool with many configuration options.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, front-loading the tool's purpose (advanced search with ripgrep). It is not overly verbose, but could be slightly expanded to include key differentiators without losing conciseness.

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?

Given the complexity of 15 parameters and no output schema or annotations, the description is too sparse. It fails to explain the tool's advanced features, return format, or typical usage scenarios, leaving the agent to infer from parameter names alone.

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?

All 15 parameters are described in the schema, achieving 100% coverage. The description adds no additional meaning or context beyond the parameter names and types, meeting the baseline for high schema coverage.

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?

The description states it's an advanced search using ripgrep with more options, clearly indicating the tool's function. However, it does not explicitly differentiate from sibling 'search' beyond implying more features, leaving some ambiguity.

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 usage guidance is provided. The description does not indicate when to use this tool over its siblings (count-matches, list-files, list-file-types, search), nor does it mention any prerequisites or restrictions.

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/shk1447/ripgrep-mcp'

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