Skip to main content
Glama
reflex-search

Reflex

Official

gather_context

Get a comprehensive overview of any codebase—structure, frameworks, entry points, file types, and more—in a single call. Ideal for quickly orienting yourself in an unfamiliar project.

Instructions

One-shot codebase orientation: structure, file types, project type, frameworks, entry points, test layout, config files. Prefer this over Glob-based recon at session start — Reflex returns a single consolidated overview instead of multiple glob calls. By default (no parameters) all context types are gathered; pass individual flags (structure, framework, entry_points, etc.) for a focused slice. Use depth to control tree depth (default 2) and path to focus on a subdirectory.

Use this for: getting oriented in an unfamiliar codebase; locating entry points; confirming which frameworks/languages are in use. For finding where a specific symbol/pattern lives, use search_code or find_references instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoFocus on specific directory path
depthNoTree depth for structure (default: 2)
frameworkNoDetect frameworks and conventions
structureNoShow directory structure
file_typesNoShow file type distribution
test_layoutNoShow test organization pattern
config_filesNoList important configuration files
entry_pointsNoShow entry point files
project_typeNoDetect project type (CLI/library/webapp/monorepo)
Behavior4/5

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

With no annotations, the description carries behavioral disclosure. It explains default behavior (all context types gathered), flag usage for focused slices, and depth/path control. It doesn't describe response format or side effects, but the read nature implies no mutation, and the consolidated overview is implied. Good but not exhaustive.

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 well-structured with separate sentences for purpose, usage guidance, and parameter details. It is slightly verbose but front-loads key actions and the recommendation. Could be more concise, but every sentence adds value.

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 9 optional parameters, no output schema, and 16 siblings, the description covers purpose, usage, parameter semantics, and differentiation. It lacks output format details, but the tool's simplicity (overview) makes this acceptable. The guidance is complete for selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and description adds significant meaning: explains each boolean flag's effect (e.g., 'Show directory structure'), clarifies defaults (depth: 2), and notes that omitting all flags gathers everything. This enriches understanding beyond the 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's purpose: 'One-shot codebase orientation' covering structure, file types, project type, frameworks, etc. It distinguishes from siblings by recommending over 'Glob-based recon' and contrasting with 'search_code' or 'find_references' for specific symbol lookup.

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?

Explicit 'Use this for' and 'instead' clauses provide clear when-to or when-not-to guidance. It identifies specific scenarios (unfamiliar codebase, locating entry points) and names alternative tools for different needs (search_code, find_references).

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