Tools
220 open-source AI tools, models, frameworks, and agents — curated from awesome-opensource-ai.
License
Language
Type
| Name↑ | Section | Lang | License | Type | Description |
|---|---|---|---|---|---|
| Anthropic / Claude Code — Bash | Anthropic / Claude CodeBash | — | — | TOOL | Executes a given bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures. Before executing the command, please follow these steps: 1. Directory Verification: - If the command will create new directories or files, first use the LS tool to verify the parent directory exists and is the correct location - For example, before running "mkdir foo/bar", first use LS to check that "foo" exists and is the intended parent directory 2. Comman |
| Anthropic / Claude Code — BashOutput | Anthropic / Claude CodeBashOutput | — | — | TOOL | - Retrieves output from a running or completed background bash shell - Takes a shell_id parameter identifying the shell - Always returns only new output since the last check - Returns stdout and stderr output along with shell status - Supports optional regex filtering to show only lines matching a pattern - Use this tool when you need to monitor or check the output of a long-running shell - Shell IDs can be found using the /bashes command |
| Anthropic / Claude Code — Edit | Anthropic / Claude CodeEdit | — | — | TOOL | Performs exact string replacements in files. Usage: - You must use your `Read` tool at least once in the conversation before editing. This tool will error if you attempt an edit without reading the file. - When editing text from Read tool output, ensure you preserve the exact indentation (tabs/spaces) as it appears AFTER the line number prefix. The line number prefix format is: spaces + line number + tab. Everything after that tab is the actual file content to match. Never include any part of |
| Anthropic / Claude Code — ExitPlanMode | Anthropic / Claude CodeExitPlanMode | — | — | TOOL | Use this tool when you are in plan mode and have finished presenting your plan and are ready to code. This will prompt the user to exit plan mode. IMPORTANT: Only use this tool when the task requires planning the implementation steps of a task that requires writing code. For research tasks where you're gathering information, searching files, reading files or in general trying to understand the codebase - do NOT use this tool. Eg. 1. Initial task: "Search for and understand the implementation |
| Anthropic / Claude Code — Glob | Anthropic / Claude CodeGlob | — | — | TOOL | - Fast file pattern matching tool that works with any codebase size - Supports glob patterns like "**/*.js" or "src/**/*.ts" - Returns matching file paths sorted by modification time - Use this tool when you need to find files by name patterns - When you are doing an open ended search that may require multiple rounds of globbing and grepping, use the Agent tool instead - You have the capability to call multiple tools in a single response. It is always better to speculatively perform multiple sea |
| Anthropic / Claude Code — Grep | Anthropic / Claude CodeGrep | — | — | TOOL | A powerful search tool built on ripgrep Usage: - ALWAYS use Grep for search tasks. NEVER invoke `grep` or `rg` as a Bash command. The Grep tool has been optimized for correct permissions and access. - Supports full regex syntax (e.g., "log.*Error", "function\s+\w+") - Filter files with glob parameter (e.g., "*.js", "**/*.tsx") or type parameter (e.g., "js", "py", "rust") - Output modes: "content" shows matching lines, "files_with_matches" shows only file paths (default), "count" shows |
| Anthropic / Claude Code — KillBash | Anthropic / Claude CodeKillBash | — | — | TOOL | - Kills a running background bash shell by its ID - Takes a shell_id parameter identifying the shell to kill - Returns a success or failure status - Use this tool when you need to terminate a long-running shell - Shell IDs can be found using the /bashes command |
| Anthropic / Claude Code — LS | Anthropic / Claude CodeLS | — | — | TOOL | Lists files and directories in a given path. The path parameter must be an absolute path, not a relative path. You can optionally provide an array of glob patterns to ignore with the ignore parameter. You should generally prefer the Glob and Grep tools, if you know which directories to search. |
| Anthropic / Claude Code — MultiEdit | Anthropic / Claude CodeMultiEdit | — | — | TOOL | This is a tool for making multiple edits to a single file in one operation. It is built on top of the Edit tool and allows you to perform multiple find-and-replace operations efficiently. Prefer this tool over the Edit tool when you need to make multiple edits to the same file. Before using this tool: 1. Use the Read tool to understand the file's contents and context 2. Verify the directory path is correct To make multiple file edits, provide the following: 1. file_path: The absolute path to |
| Anthropic / Claude Code — NotebookEdit | Anthropic / Claude CodeNotebookEdit | — | — | TOOL | Completely replaces the contents of a specific cell in a Jupyter notebook (.ipynb file) with new source. Jupyter notebooks are interactive documents that combine code, text, and visualizations, commonly used for data analysis and scientific computing. The notebook_path parameter must be an absolute path, not a relative path. The cell_number is 0-indexed. Use edit_mode=insert to add a new cell at the index specified by cell_number. Use edit_mode=delete to delete the cell at the index specified by |
| Anthropic / Claude Code — Read | Anthropic / Claude CodeRead | — | — | TOOL | Reads a file from the local filesystem. You can access any file directly by using this tool. Assume this tool is able to read all files on the machine. If the User provides a path to a file assume that path is valid. It is okay to read a file that does not exist; an error will be returned. Usage: - The file_path parameter must be an absolute path, not a relative path - By default, it reads up to 2000 lines starting from the beginning of the file - You can optionally specify a line offset and li |
| Anthropic / Claude Code — Task | Anthropic / Claude CodeTask | — | — | TOOL | Launch a new agent to handle complex, multi-step tasks autonomously. Available agent types and the tools they have access to: - general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *) - statusline-setup: Use this agent to configure the user's Cla |
| Anthropic / Claude Code — TodoWrite | Anthropic / Claude CodeTodoWrite | — | — | TOOL | Use this tool to create and manage a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user. It also helps the user understand the progress of the task and overall progress of their requests. ## When to Use This Tool Use this tool proactively in these scenarios: 1. Complex multi-step tasks - When a task requires 3 or more distinct steps or actions 2. Non-trivial and complex tasks - Tasks that require |
| Anthropic / Claude Code — WebFetch | Anthropic / Claude CodeWebFetch | — | — | TOOL | - Fetches content from a specified URL and processes it using an AI model - Takes a URL and a prompt as input - Fetches the URL content, converts HTML to markdown - Processes the content with the prompt using a small, fast model - Returns the model's response about the content - Use this tool when you need to retrieve and analyze web content Usage notes: - IMPORTANT: If an MCP-provided web fetch tool is available, prefer using that tool instead of this one, as it may have fewer restrictions. |
| Anthropic / Claude Code — WebSearch | Anthropic / Claude CodeWebSearch | — | — | TOOL | - Allows Claude to search the web and use the results to inform responses - Provides up-to-date information for current events and recent data - Returns search result information formatted as search result blocks - Use this tool for accessing information beyond Claude's knowledge cutoff - Searches are performed automatically within a single API call Usage notes: - Domain filtering is supported to include or block specific websites - Web search is only available in the US - Account for "T |
| Anthropic / Claude Code — Write | Anthropic / Claude CodeWrite | — | — | TOOL | Writes a file to the local filesystem. Usage: - This tool will overwrite the existing file if there is one at the provided path. - If this is an existing file, you MUST use the Read tool first to read the file's contents. This tool will fail if you did not read the file first. - ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required. - NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitl |
| Anthropic / Claude for Chrome — computer | Anthropic / Claude for Chromecomputer | — | — | TOOL | Use a mouse and keyboard to interact with a web browser, and take screenshots. If you don't have a valid tab ID, use tabs_context first to get available tabs. * Whenever you intend to click on an element like an icon, you should consult a screenshot to determine the coordinates of the element before moving the cursor. * If you tried clicking on a program or link but it failed to load, even after waiting, try adjusting your click location so that the tip of the cursor visually falls on the elemen |
| Anthropic / Claude for Chrome — find | Anthropic / Claude for Chromefind | — | — | TOOL | Find elements on the page using natural language. Can search for elements by their purpose (e.g., "search bar", "login button") or by text content (e.g., "organic mango product"). Returns up to 20 matching elements with references that can be used with other tools. If more than 20 matches exist, you'll be notified to use a more specific query. If you don't have a valid tab ID, use tabs_context first to get available tabs. |
| Anthropic / Claude for Chrome — form_input | Anthropic / Claude for Chromeform_input | — | — | TOOL | Set values in form elements using element reference ID from the read_page tool. If you don't have a valid tab ID, use tabs_context first to get available tabs. |
| Anthropic / Claude for Chrome — get_page_text | Anthropic / Claude for Chromeget_page_text | — | — | TOOL | Extract raw text content from the page, prioritizing article content. Ideal for reading articles, blog posts, or other text-heavy pages. Returns plain text without HTML formatting. If you don't have a valid tab ID, use tabs_context first to get available tabs. |
| Anthropic / Claude for Chrome — gif_creator | Anthropic / Claude for Chromegif_creator | — | — | TOOL | Manage GIF recording and export for browser automation sessions. Control when to start/stop recording browser actions (clicks, scrolls, navigation), then export as an animated GIF with visual overlays (click indicators, action labels, progress bar, watermark). All operations are scoped to the tab's group. When starting recording, take a screenshot immediately after to capture the initial state as the first frame. When stopping recording, take a screenshot immediately before to capture the final |
| Anthropic / Claude for Chrome — javascript_tool | Anthropic / Claude for Chromejavascript_tool | — | — | TOOL | Execute JavaScript code in the context of the current page. The code runs in the page's context and can interact with the DOM, window object, and page variables. Returns the result of the last expression or any thrown errors. If you don't have a valid tab ID, use tabs_context first to get available tabs. |
| Anthropic / Claude for Chrome — navigate | Anthropic / Claude for Chromenavigate | — | — | TOOL | Navigate to a URL, or go forward/back in browser history. If you don't have a valid tab ID, use tabs_context first to get available tabs. |
| Anthropic / Claude for Chrome — read_console_messages | Anthropic / Claude for Chromeread_console_messages | — | — | TOOL | Read browser console messages (console.log, console.error, console.warn, etc.) from a specific tab. Useful for debugging JavaScript errors, viewing application logs, or understanding what's happening in the browser console. Returns console messages from the current domain only. If you don't have a valid tab ID, use tabs_context first to get available tabs. IMPORTANT: Always provide a pattern to filter messages - without a pattern, you may get too many irrelevant messages. |
| Anthropic / Claude for Chrome — read_network_requests | Anthropic / Claude for Chromeread_network_requests | — | — | TOOL | Read HTTP network requests (XHR, Fetch, documents, images, etc.) from a specific tab. Useful for debugging API calls, monitoring network activity, or understanding what requests a page is making. Returns all network requests made by the current page, including cross-origin requests. Requests are automatically cleared when the page navigates to a different domain. If you don't have a valid tab ID, use tabs_context first to get available tabs. |
| Anthropic / Claude for Chrome — read_page | Anthropic / Claude for Chromeread_page | — | — | TOOL | Get an accessibility tree representation of elements on the page. By default returns all elements including non-visible ones. Output is limited to 50000 characters. If the output exceeds this limit, you will receive an error asking you to specify a smaller depth or focus on a specific element using ref_id. Optionally filter for only interactive elements. If you don't have a valid tab ID, use tabs_context first to get available tabs. |
| Anthropic / Claude for Chrome — resize_window | Anthropic / Claude for Chromeresize_window | — | — | TOOL | Resize the current browser window to specified dimensions. Useful for testing responsive designs or setting up specific screen sizes. If you don't have a valid tab ID, use tabs_context first to get available tabs. |
| Anthropic / Claude for Chrome — tabs_context | Anthropic / Claude for Chrometabs_context | — | — | TOOL | Get context information about all tabs in the current tab group |
| Anthropic / Claude for Chrome — tabs_create | Anthropic / Claude for Chrometabs_create | — | — | TOOL | Creates a new empty tab in the current tab group |
| Anthropic / Claude for Chrome — turn_answer_start | Anthropic / Claude for Chrometurn_answer_start | — | — | TOOL | Call this immediately before your text response to the user for this turn. Required every turn - whether or not you made tool calls. After calling, write your response. No more tools after this. |
| Anthropic / Claude for Chrome — update_plan | Anthropic / Claude for Chromeupdate_plan | — | — | TOOL | Update the plan and present it to the user for approval before proceeding. |
| Anthropic / Claude for Chrome — upload_image | Anthropic / Claude for Chromeupload_image | — | — | TOOL | Upload a previously captured screenshot or user-uploaded image to a file input or drag & drop target. Supports two approaches: (1) ref - for targeting specific elements, especially hidden file inputs, (2) coordinate - for drag & drop to visible locations like Google Docs. Provide either ref or coordinate, not both. |
| Augment Code — add_tasks | Augment Codeadd_tasks | — | — | TOOL | Add one or more new tasks to the task list. Can add a single task or multiple tasks in one call. Tasks can be added as subtasks or after specific tasks. Use this when planning complex sequences of work. |
| Augment Code — add_tasks | Augment Codeadd_tasks | — | — | TOOL | Add one or more new tasks (and optional subtasks) to the task list. |
| Augment Code — codebase-retrieval | Augment Codecodebase-retrieval | — | — | TOOL | High-level retrieval across the current codebase to locate relevant files, classes, functions, or patterns when you don't know where to look. |
| Augment Code — codebase-retrieval | Augment Codecodebase-retrieval | — | — | TOOL | This tool is Augment's context engine, the world's best codebase context engine. It: 1. Takes in a natural language description of the code you are looking for; 2. Uses a proprietary retrieval/embedding model suite that produces the highest-quality recall of relevant code snippets from across the codebase; 3. Maintains a real-time index of the codebase, so the results are always up-to-date and reflects the current state of the codebase; 4. Can retrieve across different programming languages; 5. |
| Augment Code — diagnostics | Augment Codediagnostics | — | — | TOOL | Return IDE issues (errors, warnings, etc.) for specified files. |
| Augment Code — diagnostics | Augment Codediagnostics | — | — | TOOL | Get issues (errors, warnings, etc.) from the IDE. You must provide the paths of the files for which you want to get issues. |
| Augment Code — git-commit-retrieval | Augment Codegit-commit-retrieval | — | — | TOOL | Use the repository’s commit history to find how similar changes were made in the past or why changes happened. |
| Augment Code — git-commit-retrieval | Augment Codegit-commit-retrieval | — | — | TOOL | This tool is Augment's context engine with git commit history awareness. It: 1. Takes in a natural language description of the code you are looking for; 2. Uses the git commit history as the only context for retrieval; 3. Otherwise functions like the standard codebase-retrieval tool. |
| Augment Code — grep-search | Augment Codegrep-search | — | — | TOOL | Search across multiple files/directories or the whole codebase. Use for finding text/symbols across many files. Excludes 'electron/**' by default unless explicitly overridden. |
| Augment Code — kill-process | Augment Codekill-process | — | — | TOOL | Kill a running process by terminal ID. |
| Augment Code — kill-process | Augment Codekill-process | — | — | TOOL | Kill a process by its terminal ID. |
| Augment Code — launch-process | Augment Codelaunch-process | — | — | TOOL | Launch a new process with a shell command. A process can be waiting (`wait=true`) or non-waiting (`wait=false`). If `wait=true`, launches the process in an interactive terminal, and waits for the process to complete up to `max_wait_seconds` seconds. If the process ends during this period, the tool call returns. If the timeout expires, the process will continue running in the background but the tool call will return. You can then interact with the process using the other process tools. Note: On |
| Augment Code — launch-process | Augment Codelaunch-process | — | — | TOOL | Run a shell command. Use wait=true for short commands. OS is win32; shell is 'bash'. |
| Augment Code — list-processes | Augment Codelist-processes | — | — | TOOL | List all known terminals created with the launch-process tool. |
| Augment Code — list-processes | Augment Codelist-processes | — | — | TOOL | List all known terminals created with the launch-process tool and their states. |
| Augment Code — open-browser | Augment Codeopen-browser | — | — | TOOL | Open a URL in the default browser. 1. The tool takes in a URL and opens it in the default browser. 2. The tool does not return any content. It is intended for the user to visually inspect and interact with the page. You will not have access to it. 3. You should not use `open-browser` on a URL that you have called the tool on before in the conversation history, because the page is already open in the user's browser and the user can see it and refresh it themselves. Each time you call `open-brows |
| Augment Code — open-browser | Augment Codeopen-browser | — | — | TOOL | Open a URL in the default browser. |
| Augment Code — read-process | Augment Coderead-process | — | — | TOOL | Read output from a terminal. If `wait=true` and the process has not yet completed, waits for the terminal to complete up to `max_wait_seconds` seconds before returning its output. If `wait=false` or the process has already completed, returns immediately with the current output. |
| Augment Code — read-process | Augment Coderead-process | — | — | TOOL | Read output from a previously launched process. |
| Augment Code — read-terminal | Augment Coderead-terminal | — | — | TOOL | Read output from the active or most-recently used VSCode terminal. By default, it reads all of the text visible in the terminal, not just the output of the most recent command. If you want to read only the selected text in the terminal, set `only_selected=true` in the tool input. Only do this if you know the user has selected text that you want to read. Note that this is unrelated to the list-processes and read-process tools, which interact with processes that were launched with the "launch-p |
| Augment Code — read-terminal | Augment Coderead-terminal | — | — | TOOL | Read the visible output from the active or most-recently used VSCode terminal. |
| Augment Code — remember | Augment Coderemember | — | — | TOOL | Call this tool when user asks you: - to remember something - to create memory/memories Use this tool only with information that can be useful in the long-term. Do not use this tool for temporary information. |
| Augment Code — remember | Augment Coderemember | — | — | TOOL | Store long-term memory that can be useful in future interactions. |
| Augment Code — remove-files | Augment Coderemove-files | — | — | TOOL | Remove files. ONLY use this tool to delete files in the user's workspace. This is the only safe tool to delete files in a way that the user can undo the change. Do NOT use the shell or launch-process tools to remove files. |
| Augment Code — remove-files | Augment Coderemove-files | — | — | TOOL | Delete files from the workspace in a reversible way. |
| Augment Code — render-mermaid | Augment Coderender-mermaid | — | — | TOOL | Render a Mermaid diagram from the provided definition. |
| Augment Code — render-mermaid | Augment Coderender-mermaid | — | — | TOOL | Render a Mermaid diagram from the provided definition. This tool takes Mermaid diagram code and renders it as an interactive diagram with pan/zoom controls and copy functionality. |
| Augment Code — reorganize_tasklist | Augment Codereorganize_tasklist | — | — | TOOL | Reorganize the task list structure for the current conversation. Use this only for major restructuring like reordering tasks, changing hierarchy. For individual task updates, use update_tasks tool. |
| Augment Code — reorganize_tasklist | Augment Codereorganize_tasklist | — | — | TOOL | Major restructuring of the task list using a full markdown representation. |
| Augment Code — save-file | Augment Codesave-file | — | — | TOOL | Create a new file. Does not modify existing files. |
| Augment Code — save-file | Augment Codesave-file | — | — | TOOL | Save a new file. Use this tool to write new files with the attached content. Generate `instructions_reminder` first to remind yourself to limit the file content to at most 300 lines. It CANNOT modify existing files. Do NOT use this tool to edit an existing file by overwriting it entirely. Use the str-replace-editor tool to edit existing files instead. |
| Augment Code — search-untruncated | Augment Codesearch-untruncated | — | — | TOOL | Search within previously untruncated content by reference ID. |
| Augment Code — search-untruncated | Augment Codesearch-untruncated | — | — | TOOL | Search for a term within untruncated content |
| Augment Code — str-replace-editor | Augment Codestr-replace-editor | — | — | TOOL | Tool for editing files. * `path` is a file path relative to the workspace root * `insert` and `str_replace` commands output a snippet of the edited section for each entry. This snippet reflects the final state of the file after all edits and IDE auto-formatting have been applied. * Generate `instruction_reminder` first to remind yourself to limit the edits to at most 150 lines. Notes for using the `str_replace` command: * Specify `old_str_1`, `new_str_1`, `old_str_start_line_number_1` and `old_ |
| Augment Code — str-replace-editor | Augment Codestr-replace-editor | — | — | TOOL | Edit existing files safely. Use 'str_replace' for in-place replacements with explicit line ranges, or 'insert' to insert new content at a specific line. |
| Augment Code — update_tasks | Augment Codeupdate_tasks | — | — | TOOL | Update one or more tasks' properties (state, name, description). Can update a single task or multiple tasks in one call. Use this on complex sequences of work to plan, track progress, and manage work. |
| Augment Code — update_tasks | Augment Codeupdate_tasks | — | — | TOOL | Update one or more tasks' properties (state, name, description). Prefer batch updates. |
| Augment Code — view | Augment Codeview | — | — | TOOL | View a file or directory. For files, optionally search within the file using a regex pattern or limit to a line range. Exclude the 'electron' folder by default unless explicitly requested. |
| Augment Code — view | Augment Codeview | — | — | TOOL | Custom tool for viewing files and directories and searching within files with regex query * `path` is a file or directory path relative to the workspace root * For files: displays the result of applying `cat -n` to the file * For directories: lists files and subdirectories up to 2 levels deep * If the output is long, it will be truncated and marked with `<response clipped>` Regex search (for files only): * Use `search_query_regex` to search for patterns in the file using regular expressions * U |
| Augment Code — view_tasklist | Augment Codeview_tasklist | — | — | TOOL | View the current task list for the conversation. |
| Augment Code — view_tasklist | Augment Codeview_tasklist | — | — | TOOL | View the current task list for the conversation. |
| Augment Code — view-range-untruncated | Augment Codeview-range-untruncated | — | — | TOOL | View a specific range of lines from untruncated content |
| Augment Code — view-range-untruncated | Augment Codeview-range-untruncated | — | — | TOOL | View a specific line range from previously truncated content by reference ID. |
| Augment Code — web-fetch | Augment Codeweb-fetch | — | — | TOOL | Fetch a webpage and return its content in Markdown format. |
| Augment Code — web-fetch | Augment Codeweb-fetch | — | — | TOOL | Fetches data from a webpage and converts it into Markdown. 1. The tool takes in a URL and returns the content of the page in Markdown format; 2. If the return is not valid Markdown, it means the tool cannot successfully parse this page. |
| Augment Code — web-search | Augment Codeweb-search | — | — | TOOL | Search the web using Google Custom Search API. |
| Augment Code — web-search | Augment Codeweb-search | — | — | TOOL | Search the web for information. Returns results in markdown format. Each result includes the URL, title, and a snippet from the page if available. This tool uses Google's Custom Search API to find relevant web pages. |
| Augment Code — write-process | Augment Codewrite-process | — | — | TOOL | Write input to a terminal. |
| Augment Code — write-process | Augment Codewrite-process | — | — | TOOL | Write input to a running process’s stdin. |
| Comet Assistant — tools (raw) | Comet Assistanttools.json | — | — | TOOL | Raw tool definitions from Comet Assistant |
| Cursor Prompts — codebase_search | Cursor Promptscodebase_search | — | — | TOOL | Find snippets of code from the codebase most relevant to the search query. This is a semantic search tool, so the query should ask for something semantically matching what is needed. If it makes sense to only search in particular directories, please specify them in the target_directories field. Unless there is a clear reason to use your own search query, please just reuse the user's exact query with their wording. Their exact wording/phrasing can often be helpful for the semantic search query. K |
| Cursor Prompts — create_diagram | Cursor Promptscreate_diagram | — | — | TOOL | Creates a Mermaid diagram that will be rendered in the chat UI. Provide the raw Mermaid DSL string via `content`. Use <br/> for line breaks, always wrap diagram texts/tags in double quotes, do not use custom colors, do not use :::, and do not use beta features. The diagram will be pre-rendered to validate syntax - if there are any Mermaid syntax errors, they will be returned in the response so you can fix them. |
| Cursor Prompts — delete_file | Cursor Promptsdelete_file | — | — | TOOL | Deletes a file at the specified path. The operation will fail gracefully if: - The file doesn't exist - The operation is rejected for security reasons - The file cannot be deleted |
| Cursor Prompts — edit_file | Cursor Promptsedit_file | — | — | TOOL | Use this tool to propose an edit to an existing file or create a new file. This will be read by a less intelligent model, which will quickly apply the edit. You should make it clear what the edit is, while also minimizing the unchanged code you write. When writing the edit, you should specify each edit in sequence, with the special comment `// ... existing code ...` to represent unchanged code in between edited lines. For example: ``` // ... existing code ... FIRST_EDIT // ... existing code . |
| Cursor Prompts — edit_notebook | Cursor Promptsedit_notebook | — | — | TOOL | Use this tool to edit a jupyter notebook cell. Use ONLY this tool to edit notebooks. This tool supports editing existing cells and creating new cells: - If you need to edit an existing cell, set 'is_new_cell' to false and provide the 'old_string' and 'new_string'. -- The tool will replace ONE occurrence of 'old_string' with 'new_string' in the specified cell. - If you need to create a new cell, set 'is_new_cell' to true and provide the 'new_string' (and keep 'old_string' empty). - It's cri |
| Cursor Prompts — file_search | Cursor Promptsfile_search | — | — | TOOL | Fast file search based on fuzzy matching against file path. Use if you know part of the file path but don't know where it's located exactly. Response will be capped to 10 results. Make your query more specific if need to filter results further. |
| Cursor Prompts — grep_search | Cursor Promptsgrep_search | — | — | TOOL | ### Instructions: This is best for finding exact text matches or regex patterns. This is preferred over semantic search when we know the exact symbol/function name/etc. to search in some set of directories/file types. Use this tool to run fast, exact regex searches over text files using the `ripgrep` engine. To avoid overwhelming output, the results are capped at 50 matches. Use the include or exclude patterns to filter the search scope by file type or specific paths. - Always escape special r |
| Cursor Prompts — list_dir | Cursor Promptslist_dir | — | — | TOOL | List the contents of a directory. The quick tool to use for discovery, before using more targeted tools like semantic search or file reading. Useful to try to understand the file structure before diving deeper into specific files. Can be used to explore the codebase. |
| Cursor Prompts — read_file | Cursor Promptsread_file | — | — | TOOL | Read the contents of a file. the output of this tool call will be the 1-indexed file contents from start_line_one_indexed to end_line_one_indexed_inclusive, together with a summary of the lines outside start_line_one_indexed and end_line_one_indexed_inclusive. Note that this call can view at most 250 lines at a time and 200 lines minimum. When using this tool to gather information, it's your responsibility to ensure you have the COMPLETE context. Specifically, each time you call this command yo |
| Cursor Prompts — reapply | Cursor Promptsreapply | — | — | TOOL | Calls a smarter model to apply the last edit to the specified file. Use this tool immediately after the result of an edit_file tool call ONLY IF the diff is not what you expected, indicating the model applying the changes was not smart enough to follow your instructions. |
| Cursor Prompts — run_terminal_cmd | Cursor Promptsrun_terminal_cmd | — | — | TOOL | PROPOSE a command to run on behalf of the user. If you have this tool, note that you DO have the ability to run commands directly on the USER's system. Note that the user will have to approve the command before it is executed. The user may reject it if it is not to their liking, or may modify the command before approving it. If they do change it, take those changes into account. The actual command will NOT execute until the user approves it. The user may not approve it immediately. Do NOT assum |
| Cursor Prompts — search_replace | Cursor Promptssearch_replace | — | — | TOOL | Use this tool to propose a search and replace operation on an existing file. The tool will replace ONE occurrence of old_string with new_string in the specified file. CRITICAL REQUIREMENTS FOR USING THIS TOOL: 1. UNIQUENESS: The old_string MUST uniquely identify the specific instance you want to change. This means: - Include AT LEAST 3-5 lines of context BEFORE the change point - Include AT LEAST 3-5 lines of context AFTER the change point - Include all whitespace, indentation, and s |
| Cursor Prompts — web_search | Cursor Promptsweb_search | — | — | TOOL | Search the web for real-time information about any topic. Use this tool when you need up-to-date information that might not be available in your training data, or when you need to verify current facts. The search results will include relevant snippets and URLs from web pages. This is particularly useful for questions about current events, technology updates, or any topic that requires recent information. |
| Emergent — Tools (raw) | EmergentTools.json | — | — | TOOL | Raw tool definitions from Emergent |
| Leap.new — configure_secrets | Leap.newconfigure_secrets | — | — | TOOL | Configures secret management for API keys and sensitive data |
| Leap.new — create_artifact | Leap.newcreate_artifact | — | — | TOOL | Creates a comprehensive artifact containing all project files for building full-stack applications with Encore.ts backend and React frontend |
| Leap.new — create_database_migration | Leap.newcreate_database_migration | — | — | TOOL | Creates a new SQL migration file for Encore.ts database |
| Leap.new — create_react_component | Leap.newcreate_react_component | — | — | TOOL | Creates a React component with TypeScript and Tailwind CSS |
| Leap.new — create_test_suite | Leap.newcreate_test_suite | — | — | TOOL | Creates test suites using Vitest for backend and frontend |
| Leap.new — define_backend_service | Leap.newdefine_backend_service | — | — | TOOL | Defines an Encore.ts backend service with proper structure |
| Leap.new — setup_authentication | Leap.newsetup_authentication | — | — | TOOL | Sets up authentication using Clerk for both backend and frontend |
| Leap.new — setup_object_storage | Leap.newsetup_object_storage | — | — | TOOL | Sets up object storage buckets for file uploads |
| Leap.new — setup_pubsub | Leap.newsetup_pubsub | — | — | TOOL | Sets up Pub/Sub topics and subscriptions for event-driven architecture |
| Leap.new — setup_streaming_api | Leap.newsetup_streaming_api | — | — | TOOL | Sets up streaming APIs for real-time communication |
| Lovable — Agent Tools (raw) | LovableAgent Tools.json | — | — | TOOL | Raw tool definitions from Lovable |
| Manus Agent Tools & Prompt — browser_click | Manus Agent Tools & Promptbrowser_click | — | — | TOOL | Click on elements in the current browser page. Use when clicking page elements is needed. |
| Manus Agent Tools & Prompt — browser_console_exec | Manus Agent Tools & Promptbrowser_console_exec | — | — | TOOL | Execute JavaScript code in browser console. Use when custom scripts need to be executed. |
| Manus Agent Tools & Prompt — browser_console_view | Manus Agent Tools & Promptbrowser_console_view | — | — | TOOL | View browser console output. Use when checking JavaScript logs or debugging page errors. |
| Manus Agent Tools & Prompt — browser_input | Manus Agent Tools & Promptbrowser_input | — | — | TOOL | Overwrite text in editable elements on the current browser page. Use when filling content in input fields. |
| Manus Agent Tools & Prompt — browser_move_mouse | Manus Agent Tools & Promptbrowser_move_mouse | — | — | TOOL | Move cursor to specified position on the current browser page. Use when simulating user mouse movement. |
| Manus Agent Tools & Prompt — browser_navigate | Manus Agent Tools & Promptbrowser_navigate | — | — | TOOL | Navigate browser to specified URL. Use when accessing new pages is needed. |
| Manus Agent Tools & Prompt — browser_press_key | Manus Agent Tools & Promptbrowser_press_key | — | — | TOOL | Simulate key press in the current browser page. Use when specific keyboard operations are needed. |
| Manus Agent Tools & Prompt — browser_restart | Manus Agent Tools & Promptbrowser_restart | — | — | TOOL | Restart browser and navigate to specified URL. Use when browser state needs to be reset. |
| Manus Agent Tools & Prompt — browser_scroll_down | Manus Agent Tools & Promptbrowser_scroll_down | — | — | TOOL | Scroll down the current browser page. Use when viewing content below or jumping to page bottom. |
| Manus Agent Tools & Prompt — browser_scroll_up | Manus Agent Tools & Promptbrowser_scroll_up | — | — | TOOL | Scroll up the current browser page. Use when viewing content above or returning to page top. |
| Manus Agent Tools & Prompt — browser_select_option | Manus Agent Tools & Promptbrowser_select_option | — | — | TOOL | Select specified option from dropdown list element in the current browser page. Use when selecting dropdown menu options. |
| Manus Agent Tools & Prompt — browser_view | Manus Agent Tools & Promptbrowser_view | — | — | TOOL | View content of the current browser page. Use for checking the latest state of previously opened pages. |
| Manus Agent Tools & Prompt — deploy_apply_deployment | Manus Agent Tools & Promptdeploy_apply_deployment | — | — | TOOL | Deploy website or application to public production environment. Use when deploying or updating static websites or applications. |
| Manus Agent Tools & Prompt — deploy_expose_port | Manus Agent Tools & Promptdeploy_expose_port | — | — | TOOL | Expose specified local port for temporary public access. Use when providing temporary public access for services. |
| Manus Agent Tools & Prompt — file_find_by_name | Manus Agent Tools & Promptfile_find_by_name | — | — | TOOL | Find files by name pattern in specified directory. Use for locating files with specific naming patterns. |
| Manus Agent Tools & Prompt — file_find_in_content | Manus Agent Tools & Promptfile_find_in_content | — | — | TOOL | Search for matching text within file content. Use for finding specific content or patterns in files. |
| Manus Agent Tools & Prompt — file_read | Manus Agent Tools & Promptfile_read | — | — | TOOL | Read file content. Use for checking file contents, analyzing logs, or reading configuration files. |
| Manus Agent Tools & Prompt — file_str_replace | Manus Agent Tools & Promptfile_str_replace | — | — | TOOL | Replace specified string in a file. Use for updating specific content in files or fixing errors in code. |
| Manus Agent Tools & Prompt — file_write | Manus Agent Tools & Promptfile_write | — | — | TOOL | Overwrite or append content to a file. Use for creating new files, appending content, or modifying existing files. |
| Manus Agent Tools & Prompt — idle | Manus Agent Tools & Promptidle | — | — | TOOL | A special tool to indicate you have completed all tasks and are about to enter idle state. |
| Manus Agent Tools & Prompt — info_search_web | Manus Agent Tools & Promptinfo_search_web | — | — | TOOL | Search web pages using search engine. Use for obtaining latest information or finding references. |
| Manus Agent Tools & Prompt — make_manus_page | Manus Agent Tools & Promptmake_manus_page | — | — | TOOL | Make a Manus Page from a local MDX file. |
| Manus Agent Tools & Prompt — message_ask_user | Manus Agent Tools & Promptmessage_ask_user | — | — | TOOL | Ask user a question and wait for response. Use for requesting clarification, asking for confirmation, or gathering additional information. |
| Manus Agent Tools & Prompt — message_notify_user | Manus Agent Tools & Promptmessage_notify_user | — | — | TOOL | Send a message to user without requiring a response. Use for acknowledging receipt of messages, providing progress updates, reporting task completion, or explaining changes in approach. |
| Manus Agent Tools & Prompt — shell_exec | Manus Agent Tools & Promptshell_exec | — | — | TOOL | Execute commands in a specified shell session. Use for running code, installing packages, or managing files. |
| Manus Agent Tools & Prompt — shell_kill_process | Manus Agent Tools & Promptshell_kill_process | — | — | TOOL | Terminate a running process in a specified shell session. Use for stopping long-running processes or handling frozen commands. |
| Manus Agent Tools & Prompt — shell_view | Manus Agent Tools & Promptshell_view | — | — | TOOL | View the content of a specified shell session. Use for checking command execution results or monitoring output. |
| Manus Agent Tools & Prompt — shell_wait | Manus Agent Tools & Promptshell_wait | — | — | TOOL | Wait for the running process in a specified shell session to return. Use after running commands that require longer runtime. |
| Manus Agent Tools & Prompt — shell_write_to_process | Manus Agent Tools & Promptshell_write_to_process | — | — | TOOL | Write input to a running process in a specified shell session. Use for responding to interactive command prompts. |
| NotionAi — create-database | NotionAicreate-database | — | — | TOOL | Create a new Database. Format requirements as a markdown bullet list. Each requirement should be a statement that clearly describes something you want to be true about the Database after it has been created. DO NOT try to reference the user's messages in the requirements, as the Database create sub-agent will NOT be able to see them. Make sure to include all important information in full. If you need to refer to entities in the requirements, use the entity URLs and provide context. When adding |
| NotionAi — create-pages | NotionAicreate-pages | — | — | TOOL | Creates one or more Notion pages with specified properties and content. Use create-pages when you need to create one or more new pages that don't exist yet. You can create a page with one of three options for its parent: 1. Create a top-level private page (no parent specified) 2. Create a page under another page (specify parentPageUrl) 3. Create a page in a data source (specify parentDataSourceUrl) You must choose exactly one of these three options. Examples of creating pages: 1. Create a stan |
| NotionAi — delete-pages | NotionAidelete-pages | — | — | TOOL | Deletes one or more Notion pages by moving them to trash. |
| NotionAi — query-data-sources | NotionAiquery-data-sources | — | — | TOOL | Use query-data-sources to perform a SQLite query over pages in Data Sources or query a specific view by ID. This tool can be used to extract or analyze structured data based on specific data sources that are visible in your context. Mode 1: SQL Query over Data Sources You can query and join any of the tables in the set of Data Sources in dataSourceUrls, defined by their <sqlite-table> tag. Only read-only queries are allowed. The tool will not perform UPDATE, INSERT, or DELETE operations. Make s |
| NotionAi — search | NotionAisearch | — | — | TOOL | Perform one or more searches over: - "internal": Perform semantic searches over only the user's internal Notion workspace, their connected sources (including Slack, Google Drive, Github, Jira, Microsoft Teams, Sharepoint, OneDrive, or Linear), and Notion's official help docs. - "web": Perform web searches only. Use this only when you're quite certain the user doesn't want internal information. - "default": Simultaneously do an internal search (Notion workspace, their connected sources (includin |
| NotionAi — update-database | NotionAiupdate-database | — | — | TOOL | Update a single existing Database. Format requirements as a markdown bullet list. Each requirement should be a statement that clearly describes something you want to be true about the Database after it was updated. DO NOT try to reference the user's messages in the requirements, as the Database update sub-agent will NOT be able to see them. Make sure to include all important information in full. If you need to refer to entities in the requirements, use the entity URLs and provide context. If us |
| NotionAi — update-page | NotionAiupdate-page | — | — | TOOL | Update a Notion page properties and/or content. IMPORTANT: Use this tool to add content to blank pages (indicated by <blank-page> tag in view output) instead of creating new subpages. Notion page properties are a JSON map of property names to SQLite values. For pages in a data source, use the SQLite schema definition shown in <sqlite-table>. For pages outside of a data source, the only allowed property is "title", which is the title of the page and is automatically shown at the top of the page |
| NotionAi — view | NotionAiview | — | — | TOOL | Retrieves details about Notion entities by their URLs. If you know you want to view multiple entities, you should view them ALL at once in a single tool call instead of taking multiple turns. You can view the following types of entities: - Page, ie. from a <page> block or a <mention-page> mention. This also loads it for later updates and edits. - Database, ie. from a <database> block or a <mention-database> mention - Data source, ie. from <data-sources> inside of <database> - View, ie. from a <v |
| Replit — ask_secrets | Replitask_secrets | — | — | TOOL | Ask user for the secret API keys needed for the project. If a secret is missing, use this tool as soon as possible. The secrets will be added to environment variables. This tool is very expensive to run. GOOD Examples: - To set up secure payments with Stripe, we need a STRIPE_SECRET_KEY. This key will be used to securely process payments and manage subscriptions in your application. - To enable SMS price alerts, we need Twilio API credentials TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, and TWI |
| Replit — bash | Replitbash | — | — | TOOL | Run commands in a bash shell * When invoking this tool, the contents of the "command" parameter does NOT need to be XML-escaped. * You have access to a mirror of common linux and python packages via apt and pip. * State is persistent across command calls and discussions with the user. * To inspect a particular line range of a file, e.g. lines 10-25, try 'sed -n 10,25p /path/to/the/file'. * Please avoid commands that may produce a very large amount of output. * Please run long lived commands in t |
| Replit — check_database_status | Replitcheck_database_status | — | — | TOOL | Check if given databases are available and accessible. This tool is used to verify the connection and status of specified databases. |
| Replit — check_secrets | Replitcheck_secrets | — | — | TOOL | Check if a given secret exists in the environment. This tool is used to verify the presence of a secret without exposing its actual value. |
| Replit — create_postgresql_database_tool | Replitcreate_postgresql_database_tool | — | — | TOOL | When a project requires a PostgreSQL database, you can use this tool to create a database for it. After successfully creating a database, you will have access to the following environment variables: DATABASE_URL, PGPORT, PGUSER, PGPASSWORD, PGDATABASE, PGHOST You can use these environment variables to connect to the database in your project. |
| Replit — execute_sql_tool | Replitexecute_sql_tool | — | — | TOOL | This tool allows you to execute SQL queries, fix database errors and access the database schema. ## Rules of usage: 1. Always prefer using this tool to fix database errors vs fixing by writing code like db.drop_table(table_name) 2. Provide clear, well-formatted SQL queries with proper syntax 3. Focus on database interactions, data manipulation, and query optimization ## When to use: 1. To fix and troubleshoot database-related issues 2. To explore database schema and relationships 3. To update |
| Replit — packager_tool | Replitpackager_tool | — | — | TOOL | Installs the language (if needed) and installs or uninstalls a list of libraries or project dependencies. Use this tool to install dependencies instead of executing shell commands, or editing files manually. Use this tool with language_or_system=`system` to add system-dependencies instead of using `apt install`. Installing libraries for the first time also creates the necessary project files automatically (like 'package.json', 'cargo.toml', etc). This will automatically reboot all workflows. |
| Replit — programming_language_install_tool | Replitprogramming_language_install_tool | — | — | TOOL | If a program doesn't run, you may not have the programming language installed. Use programming_language_install_tool to install it. If you need to use python, include 'python-3.11' in programming_languages. For Python 3.10, use 'python-3.10'. If you need to use Node.js, include 'nodejs-20' in programming_languages. For Node.js 18, use 'nodejs-18'. Note, this will also install the language's package manager, so don't install it separately. |
| Replit — report_progress | Replitreport_progress | — | — | TOOL | Call this function once the user explicitly confirms that a major feature or task is complete. Do not call it without the user's confirmation. Provide a concise summary of what was accomplished in the 'summary' field. This tool will ask user for the next thing to do. Don't do anything after this tool. |
| Replit — restart_workflow | Replitrestart_workflow | — | — | TOOL | Restart (or start) a workflow. |
| Replit — search_filesystem | Replitsearch_filesystem | — | — | TOOL | This tools searches and opens the relevant files for a codebase |
| Replit — shell_command_application_feedback_tool | Replitshell_command_application_feedback_tool | — | — | TOOL | This tool allows you to execute interactive shell commands and ask questions about the output or behavior of CLI applications or interactive Python programs. ## Rules of usage: 1. Provide clear, concise interactive commands to execute and specific questions about the results or interaction. 2. Ask one question at a time about the interactive behavior or output. 3. Focus on interactive functionality, user input/output, and real-time behavior. 4. Specify the exact command to run, including any ne |
| Replit — str_replace_editor | Replitstr_replace_editor | — | — | TOOL | Custom editing tool for viewing, creating and editing files * State is persistent across command calls and discussions with the user * If `path` is a file, `view` displays the result of applying `cat -n`. If `path` is a directory, `view` lists non-hidden files and directories up to 2 levels deep * The `create` command cannot be used if the specified `path` already exists as a file * If a `command` generates a long output, it will be truncated and marked with `<response clipped>` * The `undo_edi |
| Replit — suggest_deploy | Replitsuggest_deploy | — | — | TOOL | Call this function when you think the project is in a state ready for deployment. This will suggest to the user that they can deploy their project. This is a terminal action - once called, your task is complete and you should not take any further actions to verify the deployment. The deployment process will be handled automatically by Replit Deployments. ## Rules of usage: 1. Use this tool once you've validated that the project works as expected. 2. The deployment process will be handled automa |
| Replit — vnc_window_application_feedback | Replitvnc_window_application_feedback | — | — | TOOL | This tool allows you to execute interactive desktop application, which will be accessed through VNC and displayed to the user. You can ask questions about the output or behavior of this application. ## Rules of usage: 1. Provide clear, concise command to execute the application, and specific questions about the results or interaction. 2. Ask one question at a time about the interactive behavior or output. 3. Focus on interactive functionality, user input/output, and real-time behavior. 4. Speci |
| Replit — web_application_feedback_tool | Replitweb_application_feedback_tool | — | — | TOOL | This tool captures a screenshot and checks logs to verify whether the web application is running in the Replit workflow. If the application is running, the tool displays the app, asks user a question, and waits for user's response. Use this tool when the application is in a good state and the requested task is complete to avoid unnecessary delays. |
| Replit — workflows_remove_run_config_tool | Replitworkflows_remove_run_config_tool | — | — | TOOL | Remove previously added named command |
| Replit — workflows_set_run_config_tool | Replitworkflows_set_run_config_tool | — | — | TOOL | Configure a background task that executes a shell command. This is useful for starting development servers, build processes, or any other long-running tasks needed for the project. If this is a server, ensure you specify the port number it listens on in the `wait_for_port` field so the workflow isn't considered started until the server is ready to accept connections. Examples: - For a Node.js server: set `name` to 'Server', `command` to 'npm run dev', and `wait_for_port` to 5000 - For a Python |
| Same.dev — bash | Same.devbash | — | — | TOOL | Run a terminal command. Each command runs in a new shell. IMPORTANT: Do not use this tool to edit files. Use the `edit_file` tool instead. |
| Same.dev — delete_file | Same.devdelete_file | — | — | TOOL | Deletes a file at the specified path. The operation will fail gracefully if: - The file doesn't exist - The operation is rejected for security reasons - The file cannot be deleted |
| Same.dev — deploy | Same.devdeploy | — | — | TOOL | Deploys the project to Netlify. Version the project before calling this tool. Check the full-page screenshot of the live preview carefully. If the project is even borderline illegal or morally unsafe, you should not deploy it. Static vs Dynamic deployments: Netlify accepts either static or dynamic site deployments. Deploying static sites is much faster. However, if the project has a backend, API routes, or a database, deploy it as a dynamic site. For static site deployments: Use 'zip -r9' for |
| Same.dev — edit_file | Same.devedit_file | — | — | TOOL | Use this tool to make large edits or refactorings to an existing file or create a new file. Specify the `relative_file_path` argument first. `code_edit` will be read by a less intelligent model, which will quickly apply the edit. Make it clear what the edit is while minimizing the unchanged code you write. When writing the edit, specify each edit in sequence using the special comment `// ... existing code ... <description of existing code>` to represent unchanged code in between edited lines. |
| Same.dev — glob | Same.devglob | — | — | TOOL | Search for files using glob patterns. Supports patterns like *.ts, **/*.tsx, src/**/*.{js,ts}, etc. Use this when you need to find files matching specific patterns rather than fuzzy matching. |
| Same.dev — grep | Same.devgrep | — | — | TOOL | Fast text-based regex search that finds exact pattern matches within files or directories, utilizing the ripgrep command for efficient searching. Results will be formatted in the style of ripgrep and can be configured to include line numbers and content. To avoid overwhelming output, the results are capped at 50 matches. Use the include or exclude patterns to filter the search scope by file type or specific paths. This is best for finding exact text matches or regex patterns. More precise than s |
| Same.dev — ls | Same.devls | — | — | TOOL | List the contents of a directory. The quick tool to use for discovery, before using more targeted tools like semantic search or file reading. Useful to try to understand the file structure before diving deeper into specific files. Can be used to explore the codebase. |
| Same.dev — read_file | Same.devread_file | — | — | TOOL | Read the contents of a file. For text files, the output will be the 1-indexed file contents from start_line_one_indexed to end_line_one_indexed_inclusive, together with a summary of the lines outside those ranges. Notes that it can view at most 750 lines at a time. For binary files (like images), it will show you the image. When using this tool to gather information, it's your responsibility to ensure you have the COMPLETE context. Specifically, each time you call this command you should: 1) As |
| Same.dev — run_linter | Same.devrun_linter | — | — | TOOL | Before running this tool, make sure a lint script exists in the project's package.json file and all packages have been installed. This tool will return the linter result and, when available, runtime errors and dev server logs from the last time the preview was refreshed. |
| Same.dev — startup | Same.devstartup | — | — | TOOL | Shortcut to create a new web project from a framework template. Each is configured with TypeScript, Biome, and Bun. Choose the best framework for the project. Do not use this tool if the desired framework is not listed. Default to nextjs-shadcn. |
| Same.dev — string_replace | Same.devstring_replace | — | — | TOOL | Performs exact string replacements in files. Use this tool to make small, specific edits to a file. For example, to edit some text, a couple of lines of code, etc. Use edit_file for larger edits. Ensure you preserve the exact indentation (tabs/spaces) as it appears AFTER the line number prefix added by the read_file tool. Only use this tool if you are sure that the old_string is unique in the file, otherwise use the edit_file tool. The edit will FAIL if `old_string` is not unique in the file. |
| Same.dev — suggestions | Same.devsuggestions | — | — | TOOL | Suggest 1-5 next steps to implement with the USER. |
| Same.dev — task_agent | Same.devtask_agent | — | — | TOOL | Launches a highly capable task agent in the USER's workspace. Usage notes: 1. When the agent is done, it will return a report of its actions. This report is also visible to USER, so you don't have to repeat any overlapping information. 2. Each agent invocation is stateless and doesn't have access to your chat history with USER. You will not be able to send additional messages to the agent, nor will the agent be able to communicate with you outside of its final report. Therefore, your prompt shou |
| Same.dev — versioning | Same.devversioning | — | — | TOOL | Create a new version for a project. Calling this tool will automatically increment the version by 1. If there is a dev server running when the tool is called, the tool will show you a full-page screenshot of the version's live preview and return any unresolved linter and runtime errors. Create versions frequently. |
| Same.dev — web_scrape | Same.devweb_scrape | — | — | TOOL | Scrape a website to see its design and content. Use this tool to get a website's title, description, content, and screenshot (if requested). Use this tool whenever USER gives you a documentation URL to read or asks you to clone a website. When using this tool, say "I'll visit {url}..." or "I'll read {url}..." and never say "I'll scrape". |
| Same.dev — web_search | Same.devweb_search | — | — | TOOL | Search the web for real-time text and image responses. For example, you can get up-to-date information that might not be available in your training data, verify current facts, or find images that you can use in your project. You will see the text and images in the response. You can use the images by using the links in the <img> tag. Use this tool to find images you can use in your project. For example, if you need a logo, use this tool to find a logo. |
| Trae — check_command_status | Traecheck_command_status | — | — | TOOL | You can use this tool to get the status of a previously executed command by its Command ID ( non-blocking command ). |
| Trae — delete_file | Traedelete_file | — | — | TOOL | You can use this tool to delete files, you can delete multi files in one toolcall, and you MUST make sure the files is exist before deleting. |
| Trae — edit_file_fast_apply | Traeedit_file_fast_apply | — | — | TOOL | You can use this tool to edit an existing files with less than 1000 lines of code, and you should follow these rules: |
| Trae — finish | Traefinish | — | — | TOOL | The final tool of this session, when you think you have archived the goal of user requirement, you should use this tool to mark it as finish. |
| Trae — list_dir | Traelist_dir | — | — | TOOL | You can use this tool to view files of the specified directory. |
| Trae — open_preview | Traeopen_preview | — | — | TOOL | You can use this tool to show the available preview URL to user if you have started a local server successfully in a previous toolcall, which user can open it in the browser. |
| Trae — rename_file | Traerename_file | — | — | TOOL | You can use this tool to move or rename an existing file. |
| Trae — run_command | Traerun_command | — | — | TOOL | You can use this tool to PROPOSE a command to run on behalf of the user. |
| Trae — search_by_regex | Traesearch_by_regex | — | — | TOOL | Fast text-based search that finds exact pattern matches within files or directories, utilizing the ripgrep command for efficient searching. |
| Trae — search_codebase | Traesearch_codebase | — | — | TOOL | This tool is Trae's context engine. It: 1. Takes in a natural language description of the code you are looking for; 2. Uses a proprietary retrieval/embedding model suite that produces the highest-quality recall of relevant code snippets from across the codebase; 3. Maintains a real-time index of the codebase, so the results are always up-to-date and reflects the current state of the codebase; 4. Can retrieve across different programming languages; 5. Only reflects the current state of the codeba |
| Trae — stop_command | Traestop_command | — | — | TOOL | This tool allows you to terminate a currently running command( the command MUST be previously executed command. ). |
| Trae — todo_write | Traetodo_write | — | — | TOOL | Use this tool to create and manage a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user. It also helps the user understand the progress of the task and overall progress of their requests. |
| Trae — update_file | Traeupdate_file | — | — | TOOL | You can use this tool to edit file, if you think that using this tool is more cost-effective than other available editing tools, you should choose this tool, otherwise you should choose other available edit tools. |
| Trae — view_files | Traeview_files | — | — | TOOL | View up to 3 files simultaneously in batch mode for faster information gathering. |
| Trae — web_search | Traeweb_search | — | — | TOOL | This tool can be used to search the internet, which should be used with caution, as frequent searches result in a bad user experience and excessive costs. |
| Trae — write_to_file | Traewrite_to_file | — | — | TOOL | You can use this tool to write content to a file with precise control over creation/rewrite behavior. |
| Traycer AI — agent | Traycer AIagent | — | — | TOOL | Create a specialized agent for specific tasks |
| Traycer AI — explanation_response | Traycer AIexplanation_response | — | — | TOOL | - You are diligent and thorough! You NEVER leave any parts ambiguous in the explanation. - Provide clear, concise explanations that are easy to understand. - Use markdown format for better readability. |
| Traycer AI — file_outlines | Traycer AIfile_outlines | — | — | TOOL | Get a symbol outline for all files at the top level of a specified directory. This can be particularly useful when you need to understand the code present in multiple files at a high-level. |
| Traycer AI — file_search | Traycer AIfile_search | — | — | TOOL | Fast file search based on fuzzy matching against file path. Use if you know part of the file path but don't know where it's located exactly. Response will be capped to 10 results. Make your query more specific if need to filter results further. It is always better to speculatively perform multiple searches as a batch that are potentially useful. |
| Traycer AI — find_references | Traycer AIfind_references | — | — | TOOL | Find references (usage, mentions etc.) of a function, method, class, interface etc. Use this tool to jump to the all the locations where the given symbol is being used in the codebase. Software developers use this capability extensively to explore large codebases with precision. Prefer this over codebase_search when you need to lookup references of a symbol (anything tracked by LSP). You need to provide the file and line number wherever the symbol is MENTIONED. Find references tool will automati |
| Traycer AI — get_diagnostics | Traycer AIget_diagnostics | — | — | TOOL | Retrieve diagnostics for multiple files matching a glob pattern, including errors, warnings, and lint suggestions, by analyzing its code using the built-in LSP. Use this functionality to identify and resolve specific issues across multiple files that match a specific pattern. |
| Traycer AI — go_to_definition | Traycer AIgo_to_definition | — | — | TOOL | Go to Definition of a function, method, class, interface etc. Use this tool to jump to the defintion of a symbol. Software developers use this capability extensively to explore large codebases with precision. Prefer this over codebase_search when you need to lookup definitions of a symbol (anything tracked by LSP). You may provide the file and line number wherever the symbol is MENTIONED. This tool can also work just on the symbol alone although providing file and symbols will give more precise |
| Traycer AI — go_to_implementations | Traycer AIgo_to_implementations | — | — | TOOL | Use the built-in LSP to "Go to Implementations" of a given abstract class or function symbol. |
| Traycer AI — grep_search | Traycer AIgrep_search | — | — | TOOL | Fast text-based regex search that finds exact pattern matches within files or directories, utilizing the ripgrep command for efficient searching. Results will be formatted in the style of ripgrep and can be configured to include line numbers and content. To avoid overwhelming output, the results are capped at 50 matches. Use the include patterns to filter the search scope by file type or specific paths. This is best for finding exact text matches or regex patterns. More precise than codebase sea |
| Traycer AI — hand_over_to_approach_agent | Traycer AIhand_over_to_approach_agent | — | — | TOOL | Use the tool to indicate that you have explored the high-level structure of the codebase and now ready to hand over to the approach agent to write the high-level approach. |
| Traycer AI — list_dir | Traycer AIlist_dir | — | — | TOOL | List the contents of a directory. The quick tool to use for discovery, before using more targeted tools like codebase search or file reading. Useful to try to understand the file structure before diving deeper into specific files. Can be used to explore the codebase. |
| Traycer AI — phase_mode_tools (raw) | Traycer AIphase_mode_tools.json | — | — | TOOL | Raw tool definitions from Traycer AI |
| Traycer AI — read_file | Traycer AIread_file | — | — | TOOL | Read the contents of files at the specified paths. Use this when you need to examine the contents of any existing files, for example to analyze code, review text files, or extract information from configuration files. For large files, the system will provide a structured summary with line ranges and brief descriptions of each section instead of the full content. You can then request specific line ranges after reviewing the summary using the read_partial_file tool. Automatically extracts raw text |
| Traycer AI — read_partial_file | Traycer AIread_partial_file | — | — | TOOL | Read specific line ranges from files at the specified paths. Use this when you need to examine only portions of files rather than their entire contents, which is useful for when you only need to focus on specific sections of code, configuration files, or text documents. Specify the startLine and numberOfLines properties for each path to control exactly which portion of the file you want to read. This is more efficient than reading entire files when you only need specific sections. |
| Traycer AI — think | Traycer AIthink | — | — | TOOL | Use the tool to think about something. It will not obtain new information or make any changes to the repository, but just log the thought. Use it when complex reasoning or brainstorming is needed. |
| Traycer AI — web_search | Traycer AIweb_search | — | — | TOOL | Performs web searches to find relevant information and documentation for the given query. This tool helps gather external knowledge useful for solving tasks, especially for obtaining the latest information or documentation. |
| v0 Prompts and Tools — FetchFromWeb | v0 Prompts and ToolsFetchFromWeb | — | — | TOOL | Fetches full text content from web pages when you have specific URLs to read. Returns clean, parsed text with metadata. **When to use:** • **Known URLs** - You have specific pages/articles you need to read completely • **Deep content analysis** - Need full text, not just search result snippets • **Documentation reading** - External docs, tutorials, or reference materials • **Follow-up research** - After web search, fetch specific promising results **What you get:** • Complete page text conte |
| v0 Prompts and Tools — GenerateDesignInspiration | v0 Prompts and ToolsGenerateDesignInspiration | — | — | TOOL | Generate design inspiration to ensure your generations are visually appealing. When to use: - Vague design requests - User asks for "a nice landing page" or "modern dashboard" - Creative enhancement needed - Basic requirements need visual inspiration and specificity - Design direction required - No clear aesthetic, color scheme, or visual style provided - Complex UI/UX projects - Multi-section layouts, branding, or user experience flows Skip when: - Backend/API work - No visual design compone |
| v0 Prompts and Tools — GetOrRequestIntegration | v0 Prompts and ToolsGetOrRequestIntegration | — | — | TOOL | Checks integration status, retrieves environment variables, and gets live database schemas. Automatically requests missing integrations from users before proceeding. **What it provides:** • **Integration status** - Connected services and configuration state • **Environment variables** - Available project env vars and missing requirements • **Live database schemas** - Real-time table/column info for SQL integrations, RLS policies for tables if configured (Supabase, Neon, etc.). Use this instead |
| v0 Prompts and Tools — GrepRepo | v0 Prompts and ToolsGrepRepo | — | — | TOOL | Searches for regex patterns within file contents across the repository. Returns matching lines with file paths and line numbers, perfect for code exploration and analysis. Primary use cases: • Find function definitions: 'function\s+myFunction' or 'const\s+\w+\s*=' • Locate imports/exports: 'import.*from' or 'export\s+(default|\{)' • Search for specific classes: 'class\s+ComponentName' or 'interface\s+\w+' • Find API calls: 'fetch\(' or 'api\.(get|post)' • Discover configuration: 'process\.env' |
| v0 Prompts and Tools — InspectSite | v0 Prompts and ToolsInspectSite | — | — | TOOL | Takes screenshots to verify user-reported visual bugs or capture reference designs from live websites for recreation. **Use for:** • **Visual bug verification** - When users report layout issues, misaligned elements, or styling problems • **Website recreation** - Capturing reference designs (e.g., "recreate Nike homepage", "copy Stripe's pricing page") **Technical:** Converts localhost URLs to preview URLs, optimizes screenshot sizes, supports multiple URLs. |
| v0 Prompts and Tools — LSRepo | v0 Prompts and ToolsLSRepo | — | — | TOOL | Lists files and directories in the repository. Returns file paths sorted alphabetically with optional pattern-based filtering. Common use cases: • Explore repository structure and understand project layout • Find files in specific directories (e.g., 'src/', 'components/') • Locate configuration files, documentation, or specific file types • Get overview of available files before diving into specific areas Tips: • Use specific paths to narrow down results (max 200 entries returned) • Combine wi |
| v0 Prompts and Tools — ReadFile | v0 Prompts and ToolsReadFile | — | — | TOOL | Reads file contents intelligently - returns complete files when small, paginated chunks, or targeted chunks when large based on your query. **How it works:** • **Small files** (≤2000 lines) - Returns complete content • **Large files** (>2000 lines) - Uses AI to find and return relevant chunks based on query • **Binary files** - Returns images, handles blob content appropriately • Any lines longer than 2000 characters are truncated for readability • Start line and end line can be provided to rea |
| v0 Prompts and Tools — SearchRepo | v0 Prompts and ToolsSearchRepo | — | — | TOOL | Launches a new agent that searches and explores the codebase using multiple search strategies (grep, file listing, content reading). Returns relevant files and contextual information to answer queries about code structure, functionality, and content. **Core capabilities:** - File discovery and content analysis across the entire repository - Pattern matching with regex search for specific code constructs - Directory exploration and project structure understanding - Intelligent file selection a |
| v0 Prompts and Tools — SearchWeb | v0 Prompts and ToolsSearchWeb | — | — | TOOL | Performs intelligent web search using high-quality sources and returns comprehensive, cited answers. Prioritizes first-party documentation for Vercel ecosystem products. Primary use cases: - Technology documentation - Latest features, API references, configuration guides - Current best practices - Up-to-date development patterns and recommendations - Product-specific information - Vercel, Next.js, AI SDK, and ecosystem tools - Version-specific details - New releases, breaking changes, migrati |
| v0 Prompts and Tools — TodoManager | v0 Prompts and ToolsTodoManager | — | — | TOOL | Manages structured todo lists for complex, multi-step projects. Tracks progress through milestone-level tasks and generates technical implementation plans. **Core workflow:** 1. **set_tasks** - Break project into 3-7 milestone tasks (distinct systems, major features, integrations) 2. **move_to_task** - Complete current work, focus on next task **Task guidelines:** • **Milestone-level tasks** - "Build Homepage", "Setup Auth", "Add Database" (not micro-steps) • **One page = one task** - Don't br |