<when_to_use> Call this first before searching any new codebase Required prerequisite for search_codebase </when_to_use>

<parameter name="force_reindex" required="false">
  <type>boolean</type>
  <description>Force complete reindexing even if already indexed</description>
  <default>false</default>
  <when_to_use>Code has changed significantly or search results seem outdated</when_to_use>
</parameter>

<when_to_use> Find specific functions, classes, or code patterns Get context before making changes to understand dependencies Explore how existing systems work Locate examples of API usage or patterns </when_to_use>

<parameter name="codebase_path" required="true">
  <type>string</type>
  <description>ABSOLUTE path to the codebase directory to search</description>
  <examples>
    <valid>/Users/name/project</valid>
    <valid>/home/user/code/repo</valid>
    <invalid>.</invalid>
    <invalid>../project</invalid>
    <invalid>relative/path</invalid>
  </examples>
  <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation>
</parameter>

<parameter name="max_results" required="false">
  <type>number</type>
  <description>Maximum number of code chunks to return</description>
  <default>5</default>
  <best_practice>Keep at default 5 for focused results. Use multiple targeted searches rather than increasing this limit</best_practice>
</parameter>

<result_interpretation> Results ranked by semantic relevance, not code importance Implementation code often appears in results 2-5, not just #1 Look for actual code files (.ts, .js, .sql) over documentation (.md, .txt) </result_interpretation>

Code chunks with file paths, line numbers, relevance scores, symbol information, imports, and exports Codebase must be indexed first with index_codebase

<enhanced_features> Shows completion statistics for finished indexing (success rates, processing time, performance metrics) Displays batch processing details (successful/skipped batches) References log files for detailed debugging </enhanced_features>

<when_to_use> Before indexing to check if already done After indexing to see completion statistics and success rates Debug why search returned no results Confirm indexing completed successfully Get overview of all indexed codebases </when_to_use>

Enhanced indexing status with completion statistics when available

<when_to_use> Clear stale data before reindexing after major code changes Remove old indexed codebases no longer needed Fix corrupted index causing search issues </when_to_use>