|
|
@@ -30,19 +30,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -365,19 +393,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -789,19 +845,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -1177,19 +1261,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -1512,19 +1624,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -1847,19 +1987,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -2182,19 +2350,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -2566,19 +2762,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -3355,19 +3579,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -3739,19 +3991,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -4136,19 +4416,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -4513,19 +4821,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -5010,19 +5346,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -5421,19 +5785,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
|
|
@@ -5730,19 +6122,47 @@ Always adhere to this format for the tool use to ensure proper parsing and execu
|
|
|
# Tools
|
|
|
|
|
|
## read_file
|
|
|
-Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
+Description: Request to read the contents of a file at the specified path. Use this when you need to examine the contents of an existing file you do not know the contents of, for example to analyze code, review text files, or extract information from configuration files. The output includes line numbers prefixed to each line (e.g. "1 | const x = 1"), making it easier to reference specific lines when creating diffs or discussing code. By specifying start_line and end_line parameters, you can efficiently read specific portions of large files without loading the entire file into memory. Automatically extracts raw text from PDF and DOCX files. May not be suitable for other types of binary files, as it returns the raw content as a string.
|
|
|
Parameters:
|
|
|
- path: (required) The path of the file to read (relative to the current working directory /test/path)
|
|
|
+- start_line: (optional) The starting line number to read from (1-based). If not provided, it starts from the beginning of the file.
|
|
|
+- end_line: (optional) The ending line number to read to (1-based, inclusive). If not provided, it reads to the end of the file.
|
|
|
Usage:
|
|
|
<read_file>
|
|
|
<path>File path here</path>
|
|
|
+<start_line>Starting line number (optional)</start_line>
|
|
|
+<end_line>Ending line number (optional)</end_line>
|
|
|
</read_file>
|
|
|
|
|
|
-Example: Requesting to read frontend-config.json
|
|
|
+Examples:
|
|
|
+
|
|
|
+1. Reading an entire file:
|
|
|
<read_file>
|
|
|
<path>frontend-config.json</path>
|
|
|
</read_file>
|
|
|
|
|
|
+2. Reading the first 1000 lines of a large log file:
|
|
|
+<read_file>
|
|
|
+<path>logs/application.log</path>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+3. Reading lines 500-1000 of a CSV file:
|
|
|
+<read_file>
|
|
|
+<path>data/large-dataset.csv</path>
|
|
|
+<start_line>500</start_line>
|
|
|
+<end_line>1000</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+4. Reading a specific function in a source file:
|
|
|
+<read_file>
|
|
|
+<path>src/app.ts</path>
|
|
|
+<start_line>46</start_line>
|
|
|
+<end_line>68</end_line>
|
|
|
+</read_file>
|
|
|
+
|
|
|
+Note: When both start_line and end_line are provided, this tool efficiently streams only the requested lines, making it suitable for processing large files like logs, CSV files, and other large datasets without memory issues.
|
|
|
+
|
|
|
## search_files
|
|
|
Description: Request to perform a regex search across files in a specified directory, providing context-rich results. This tool searches for patterns or specific content across multiple files, displaying each match with encapsulating context.
|
|
|
Parameters:
|
Sam Hoang Van