Skip to main content
Glama
reflex-search

Reflex

Official

list_locations

Find file and line numbers for all occurrences of a pattern. Returns array of path and line objects for efficient location enumeration.

Instructions

Cheapest way to find every place a pattern occurs. Prefer this over Glob-based path hunting and over Grep when you only need file + line numbers (no previews). Returns an array of {path, line} objects — one per match, no limit.

Use this for: enumerating locations before deciding which files to Read; counting affected sites; listing all hits of a pattern without paying for previews. Supports lang, file, glob, exclude filters.

Example: pattern: "CourtCase"[{"path": "app/Models/CourtCase.php", "line": 15}, {"path": "app/Http/Controllers/CourtController.php", "line": 42}]. On "Index not found" / "stale" error, call index_project, then retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoFilter by file path substring (e.g., 'Controllers')
globNoInclude files matching patterns (e.g., ['app/**/*.php'])
langNoFilter by language (php, rust, typescript, python, etc.)
forceNoForce execution of potentially expensive queries (bypasses broad query detection)
excludeNoExclude files matching patterns (e.g., ['vendor/**', 'tests/**'])
patternYesSearch pattern (text to find)
dependenciesNoInclude dependency information (imports) in results. Only extracts static imports.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses there is no result limit, mentions error handling ('Index not found' -> call index_project), and implies read-only operation. Doesn't describe side effects or resource usage in depth, but sufficient.

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?

Description is well-structured with purpose, usage, example, and error handling. Could be slightly more concise, but front-loads the key purpose and differentiation.

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 7 parameters and no output schema, description covers output format, error recovery, and usage context. Lacks detail on some parameters like 'dependencies', but overall sufficient for agent decision-making.

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. Description adds little beyond listing supported filters and providing an example; does not explain 'force' or 'dependencies' beyond 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?

The description clearly states the tool finds every place a pattern occurs, returns file+line objects, and explicitly distinguishes it from Glob and Grep. It also mentions the output format with an example.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use scenarios (enumerating locations before reading, counting hits, listing without previews). Does not explicitly state when not to use it, but contrasts with alternatives upfront.

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/reflex-search/reflex'

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