Skip to main content
Glama
blas0

rev-eng-cursor-regex-mcp

by blas0

Search Literal

search.literal
Read-only

Search for an exact string in workspace files. Narrow results with glob patterns and include surrounding context lines.

Instructions

Find exact text in indexed workspace files. Prefer this over regex when you already know the exact string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
needleYesExact text to search for without any regex syntax.
pathGlobsNoOptional relative glob patterns that narrow the search to specific folders or files.
afterLinesNoNumber of context lines to include after each match. Defaults to 1.
maxResultsNoMaximum number of matches to return. Defaults to 100.
beforeLinesNoNumber of context lines to include before each match. Defaults to 1.
caseSensitiveNoSet to false to perform a case-insensitive full-text match.
workspaceRootNoAbsolute workspace root to search. Defaults to the server workspace.
autoEnsureIndexNoRefresh the local index automatically before searching. Defaults to true.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
planNo
matchesYes
elapsedMsYes
queryKindYes
truncatedYes
matchCountYes
plannerModeNo
fallbackReasonNo
scannedDocCountYes
candidateDocCountYes
coveringGramCountNo
extractableAnchorsNo
Behavior3/5

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

Annotations provide readOnlyHint and openWorldHint, so safety is clear. The description adds 'indexed workspace files' context but does not elaborate on pagination, performance, or other behaviors beyond what annotations cover.

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 sentences that convey purpose and usage guidance with zero wasted words. Perfectly sized and front-loaded.

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 the 8 parameters, existing output schema, and annotations, the description covers essential purpose and usage. It could add more about interaction with index tools or autoEnsureIndex behavior, but overall it's sufficiently complete.

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 baseline is 3. The description provides no parameter-specific details beyond what the schema already documents.

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 states 'Find exact text in indexed workspace files' with a specific verb ('Find') and resource ('exact text in indexed workspace files'). It also distinguishes from sibling 'search.regex' by advising preference when exact string is known.

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 advises 'Prefer this over regex when you already know the exact string', giving clear when-to-use guidance and naming the alternative (regex).

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/blas0/rev-eng-cursor-regex-mcp'

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