610 lines
54 KiB
JSON
610 lines
54 KiB
JSON
|
[
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Executes a given command in a shell session with optional foreground timeout.\n\nPLAN MODE SAFETY: In plan mode, Shell is only for readonly diagnostics or checks that do not modify tracked or untracked workspace files. Do NOT use Shell in plan mode to create, write, edit, delete, move, copy, generate, format, or commit files. Forbidden examples include mkdir, touch, cat with redirection or heredoc, echo with redirection, tee, cp, mv, rm, sed -i, formatters, code generators, package-manager commands that update manifests or lockfiles, and any command whose purpose is to place content into the workspace. If the user asks for such an action, update or create a plan with CreatePlan instead.\n\nIMPORTANT: This tool is for terminal operations like git, npm, docker, etc. DO NOT use it for file operations (reading, writing, editing, searching, finding files) - use the specialized tools for this instead.\n\nBefore executing the command, please follow these steps:\n\n1. Check for Running Processes:\n - Before starting dev servers or long-running processes that should not be duplicated, list the terminals folder to check if they are already running in existing terminals.\n - You can use this information to determine which terminal, if any, matches the command you want to run, contains the output from the command you want to inspect, or has changed since you last read them.\n - Since these are text files, you can read any terminal's contents simply by reading the file, search using Grep, etc.\n2. Directory Verification:\n - If the command will create new directories or files, first run ls to verify the parent directory exists and is the correct location\n - For example, before running \"mkdir foo/bar\", first run 'ls' to check that \"foo\" exists and is the intended parent directory\n3. Command Execution:\n - Always quote file paths that contain spaces with double quotes (e.g., cd \"path with spaces/file.txt\")\n - Examples of proper quoting:\n - cd \"/Users/name/My Documents\" (correct)\n - cd /Users/name/My Documents (incorrect - will fail)\n - python \"/path/with spaces/script.py\" (correct)\n - python /path/with spaces/script.py (incorrect - will fail)\n - After ensuring proper quoting, execute the command.\n - Capture the output of the command.\n\nUsage notes:\n\n- The command argument is required.\n- The shell starts in the workspace root and is stateful across sequential calls. Current working directory and environment variables persist between calls. Use the `working_directory` parameter to run commands in different directories. Example: to run `npm install` in the `frontend` folder, set `working_directory: \"frontend\"` rather than using `cd frontend && npm install`.\n- It is very helpful if you write a clear, concise description of what this command does in 5-10 words.\n- VERY IMPORTANT: You MUST avoid using search commands like `find` and `grep`.Instead use Grep, Glob to search.You MUST avoid read tools like `cat`, `head`, and `tail`, and use Read to read files.Avoid editing files with tools like `sed` and `awk`; in plan mode, describe the intended edit in the plan instead of modifying files.\n- If you _still_ need to run `grep`, STOP. ALWAYS USE ripgrep at `rg` first, which all users have pre-installed.\n- When issuing multiple commands:\n - If the commands are independent and can run in parallel, make multiple Shell tool calls in a single message. For example, if you need to run \"git status\" and \"git diff\", send a single message with two Shell tool calls in parallel.\n - If the commands depend on each other and must run sequentially, use a single Shell call with '&&' to chain them together (e.g., `git add . && git commit -m \"message\" && git push`). For instance, if one operation must complete before another starts (like mkdir before cp,Write before Shell for git operations, or git add before git commit), run these operations sequentially instead.\n - Use ';' only when you need to run commands sequentially but don't care if earlier commands fail\n - DO NO
|
||
|
|
"name": "Shell",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"block_until_ms": {
|
||
|
|
"description": "How long to block and wait for the command to complete before moving it to background (in milliseconds). Defaults to 30000ms (30 seconds). Set to 0 to immediately run the command in the background. The timer includes the shell startup time.",
|
||
|
|
"type": "number"
|
||
|
|
},
|
||
|
|
"command": {
|
||
|
|
"description": "The command to execute",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"description": {
|
||
|
|
"description": "Clear, concise description of what this command does in 5-10 words",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"working_directory": {
|
||
|
|
"description": "The absolute path to the working directory to execute the command in (defaults to current directory)",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"notify_on_output": {
|
||
|
|
"description": "Optional watcher for backgrounded command output. You will be notified at the end of your turn whenever output matches the regex pattern. Use stable sentinel lines and simple anchored regexes; do not match all output. Completion notifications are separate and do not require this field.",
|
||
|
|
"properties": {
|
||
|
|
"pattern": {
|
||
|
|
"description": "Regex pattern to match against command output.",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"reason": {
|
||
|
|
"description": "Five or fewer words describing what you are watching for. The UI prefixes it as Monitored `reason`.",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"debounce_ms": {
|
||
|
|
"description": "Minimum milliseconds between notifications. Values below 5000ms are treated as 5000ms.",
|
||
|
|
"type": "number"
|
||
|
|
},
|
||
|
|
"notification_limit": {
|
||
|
|
"description": "Optional maximum number of output-match notifications for this command.",
|
||
|
|
"type": "number"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"pattern",
|
||
|
|
"reason"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"command"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"type": "function",
|
||
|
|
"function": {
|
||
|
|
"name": "AwaitShell",
|
||
|
|
"description": "Check or poll a backgrounded shell job. Use this after Shell returns a shell_id. If shell_id is omitted, this waits for the requested block_until_ms duration and returns. Prefer not to poll reflexively; use it when the next step depends on the background job status or when doing a one-shot smoke check after block_until_ms: 0. Pattern matching checks accumulated stdout/stderr content, not terminal metadata.",
|
||
|
|
"parameters": {
|
||
|
|
"type": "object",
|
||
|
|
"properties": {
|
||
|
|
"shell_id": {
|
||
|
|
"type": "string",
|
||
|
|
"description": "Optional shell id to poll. Required when block_until_ms is 0."
|
||
|
|
},
|
||
|
|
"block_until_ms": {
|
||
|
|
"type": "number",
|
||
|
|
"description": "Max time to wait before returning, in milliseconds. Defaults to 30000ms. Set to 0 for a non-blocking status check."
|
||
|
|
},
|
||
|
|
"pattern": {
|
||
|
|
"type": "string",
|
||
|
|
"description": "Regex pattern to match against accumulated stdout/stderr content. Uses multiline matching."
|
||
|
|
}
|
||
|
|
}
|
||
|
|
}
|
||
|
|
}
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Writes literal characters to an existing background shell session. PLAN MODE SAFETY: only use this for readonly diagnostic shell sessions. Use only when a previous Shell result returned a shell_id and the process is waiting for stdin. Include any needed newline in chars.",
|
||
|
|
"name": "WriteShellStdin",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"chars": {
|
||
|
|
"description": "Literal characters to write to stdin. Include \\n when submitting a line.",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"shell_id": {
|
||
|
|
"description": "The shell_id returned by a backgrounded Shell command.",
|
||
|
|
"type": "number"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"shell_id",
|
||
|
|
"chars"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Requests that a running Shell tool call move to the background so the current agent turn can continue. Pass the original Shell tool_call_id, not the shell_id.",
|
||
|
|
"name": "ForceBackgroundShell",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"tool_call_id": {
|
||
|
|
"description": "The original Shell tool call id to move to background.",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"tool_call_id"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "\nTool to search for files matching a glob pattern\n\n- Works fast with codebases of any size\n- Returns matching file paths sorted by modification time\n- Use this tool when you need to find files by name patterns\n- You have the capability to call multiple tools in a single response. It is always better to speculatively perform multiple searches that are potentially useful as a batch.\n",
|
||
|
|
"name": "Glob",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"glob_pattern": {
|
||
|
|
"description": "The glob pattern to match files against.\nPatterns not starting with \"**/\" are automatically prepended with \"**/\" to enable recursive searching.\n\nExamples:\n\t- \"*.js\" (becomes \"**/*.js\") - find all .js files\n\t- \"**/node_modules/**\" - find all node_modules directories\n\t- \"**/test/**/test_*.ts\" - find all test_*.ts files in any test directory",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"target_directory": {
|
||
|
|
"description": "Absolute path to directory to search for files in. If not provided, defaults to Cursor workspace root.",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"glob_pattern"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "A powerful search tool built on ripgrep\nUsage:\n- Prefer using Grep for search tasks when you know the exact symbols or strings to search for. Whenever possible, use this tool instead of invoking grep or rg as a terminal command. The Grep tool has been optimized for speed and file restrictions inside Cursor.\n- Supports full regex syntax (e.g., \"log.*Error\", \"function\\s+\\w+\")\n- Filter files with glob parameter (e.g., \".js\", \"**/.tsx\") or type parameter (e.g., \"js\", \"py\", \"rust\")\n- Output modes: \"content\" shows matching lines (default), \"files_with_matches\" shows only file paths, \"count\" shows match counts\n- Pattern syntax: Uses ripgrep (not grep) - literal braces need escaping (use interface\\{\\} to find interface{} in Go code)\n- Multiline matching: By default patterns match within single lines only. For cross-line patterns like struct \\{[\\s\\S]*?field, use multiline: true\n- Results are capped to several thousand output lines for responsiveness; when truncation occurs, the results report \"at least\" counts, but are otherwise accurate.\n- Content output formatting closely follows ripgrep output format: '-' for context lines, ':' for match lines, and all context/match lines below each file group.",
|
||
|
|
"name": "Grep",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"-A": {
|
||
|
|
"description": "Number of lines to show after each match (rg -A). Requires output_mode: \"content\", ignored otherwise.",
|
||
|
|
"type": "number"
|
||
|
|
},
|
||
|
|
"-B": {
|
||
|
|
"description": "Number of lines to show before each match (rg -B). Requires output_mode: \"content\", ignored otherwise.",
|
||
|
|
"type": "number"
|
||
|
|
},
|
||
|
|
"-C": {
|
||
|
|
"description": "Number of lines to show before and after each match (rg -C). Requires output_mode: \"content\", ignored otherwise.",
|
||
|
|
"type": "number"
|
||
|
|
},
|
||
|
|
"-i": {
|
||
|
|
"description": "Case insensitive search (rg -i) Defaults to false",
|
||
|
|
"type": "boolean"
|
||
|
|
},
|
||
|
|
"glob": {
|
||
|
|
"description": "Glob pattern to filter files (e.g. \"*.js\", \"*.{ts,tsx}\") - maps to rg --glob",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"head_limit": {
|
||
|
|
"description": "Limit output size. For \"content\" mode: limits total matches shown. For \"files_with_matches\" and \"count\" modes: limits number of files.",
|
||
|
|
"minimum": 0,
|
||
|
|
"type": "number"
|
||
|
|
},
|
||
|
|
"multiline": {
|
||
|
|
"description": "Enable multiline mode where . matches newlines and patterns can span lines (rg -U --multiline-dotall). Default: false.",
|
||
|
|
"type": "boolean"
|
||
|
|
},
|
||
|
|
"offset": {
|
||
|
|
"description": "Skip first N entries. For \"content\" mode: skips first N matches. For \"files_with_matches\" and \"count\" modes: skips first N files. Use with head_limit for pagination.",
|
||
|
|
"minimum": 0,
|
||
|
|
"type": "number"
|
||
|
|
},
|
||
|
|
"output_mode": {
|
||
|
|
"description": "Output mode: \"content\" shows matching lines (supports -A/-B/-C context, -n line numbers, head_limit), \"files_with_matches\" shows file paths (supports head_limit), \"count\" shows match counts (supports head_limit). Defaults to \"content\".",
|
||
|
|
"enum": [
|
||
|
|
"content",
|
||
|
|
"files_with_matches",
|
||
|
|
"count"
|
||
|
|
],
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"path": {
|
||
|
|
"description": "File or directory to search in (rg pattern -- PATH). Defaults to Cursor workspace root.",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"pattern": {
|
||
|
|
"description": "The regular expression pattern to search for in file contents",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"type": {
|
||
|
|
"description": "File type to search (rg --type). Common types: js, py, rust, go, java, etc. More efficient than include for standard file types.",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"pattern"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Reads a file from the local filesystem. You can access any file directly by using this tool.\nIf 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.\n\nUsage:\n- You can optionally specify a line offset and limit (especially handy for long files), but it's recommended to read the whole file by not providing these parameters\n- Lines in the output are numbered starting at 1, using following format: LINE_NUMBER|LINE_CONTENT\n- You have the capability to call multiple tools in a single response. It is always better to speculatively read multiple files as a batch that are potentially useful.\n- If you read a file that exists but has empty contents you will receive 'File is empty.'\n\nImage Support:\n- This tool can also read image files when called with the appropriate path.\n- Supported image formats: jpeg/jpg, png, gif, webp.\n\nPDF Support:\n- PDF files are converted into text content automatically (subject to the same character limits as other files).",
|
||
|
|
"name": "Read",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"limit": {
|
||
|
|
"description": "The number of lines to read. Only provide if the file is too large to read at once.",
|
||
|
|
"type": "integer"
|
||
|
|
},
|
||
|
|
"offset": {
|
||
|
|
"description": "The line number to start reading from. Positive values are 1-indexed from the start of the file. Negative values count backwards from the end (e.g. -1 is the last line). Only provide if the file is too large to read at once.",
|
||
|
|
"type": "integer"
|
||
|
|
},
|
||
|
|
"path": {
|
||
|
|
"description": "The absolute path of the file to read.",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"path"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Lists files and directories under a directory path.\n\nUse this tool when you need directory structure, especially top-level project layout or immediate children of a folder. Do not use Glob(\"*\") or recursive Glob patterns to list a directory; use Ls instead.\n\nYou may provide ignore globs for large or irrelevant directories such as .git, node_modules, dist, build, .cursor-local-assistant-v2/history, or logs.",
|
||
|
|
"name": "Ls",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"ignore": {
|
||
|
|
"description": "Optional ignore globs for directories or files that should be skipped while listing.",
|
||
|
|
"items": {
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"type": "array"
|
||
|
|
},
|
||
|
|
"path": {
|
||
|
|
"description": "The absolute path of the directory to list.",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"path"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Use this tool to create and manage a structured task list for your current coding session. This helps track progress, organize complex tasks, and demonstrate thoroughness.\n\nNote: Other than when first creating todos, don't tell the user you're updating todos, just do it.\n\n### When to Use This Tool\n\nUse proactively for:\n1. Complex multi-step tasks (3+ distinct steps)\n2. Non-trivial tasks requiring careful planning\n3. User explicitly requests todo list\n4. User provides multiple tasks (numbered/comma-separated)\n5. After receiving new instructions - capture requirements as todos (use merge=true to add or update them unless you are providing a complete replacement list)\n6. After completing tasks - mark complete with merge=true and add follow-ups\n7. When starting new tasks - mark as in_progress (ideally only one at a time)\n\n### When NOT to Use\n\nSkip for:\n1. Single, straightforward tasks\n2. Trivial tasks with no organizational benefit\n3. Tasks completable in < 3 trivial steps\n4. Purely conversational/informational requests\n5. Don't add a task to test the change unless asked, or you'll overfocus on testing\n\n### Examples\n\n<example>\n User: Add dark mode toggle to settings\n Assistant:\n - *Creates todo list:*\n 1. Add state management [in_progress]\n 2. Implement styles\n 3. Create toggle component\n 4. Update components\n - [Immediately begins working on todo 1 in the same tool call batch]\n<reasoning>\n Multi-step feature with dependencies.\n</reasoning>\n</example>\n\n<example>\n User: Rename getCwd to getCurrentWorkingDirectory across my project\n Assistant: *Searches codebase, finds 15 instances across 8 files*\n *Creates todo list with specific items for each file that needs updating*\n\n<reasoning>\n Complex refactoring requiring systematic tracking across multiple files.\n</reasoning>\n</example>\n\n<example>\n User: Implement user registration, product catalog, shopping cart, checkout flow.\n Assistant: *Creates todo list breaking down each feature into specific tasks*\n\n<reasoning>\n Multiple complex features provided as list requiring organized task management.\n</reasoning>\n</example>\n\n<example>\n User: Optimize my React app - it's rendering slowly.\n Assistant: *Analyzes codebase, identifies issues*\n *Creates todo list: 1) Memoization, 2) Virtualization, 3) Image optimization, 4) Fix state loops, 5) Code splitting*\n\n<reasoning>\n Performance optimization requires multiple steps across different components.\n</reasoning>\n</example>\n\n### Examples of When NOT to Use the Todo List\n\n<example>\n User: What does git status do?\n Assistant: Shows current state of working directory and staging area...\n\n<reasoning>\n Informational request with no coding task to complete.\n</reasoning>\n</example>\n\n<example>\n User: Add comment to calculateTotal function.\n Assistant: *Uses edit tool to add comment*\n\n<reasoning>\n Single straightforward task in one location.\n</reasoning>\n</example>\n\n<example>\n User: Run npm install for me.\n Assistant: *Executes npm install* Command completed successfully...\n\n<reasoning>\n Single command execution with immediate results.\n</reasoning>\n</example>\n\n### Task States and Management\n\n1. **Task States:**\n - pending: Not yet started\n - in_progress: Currently working on\n - completed: Finished successfully\n - cancelled: No longer needed\n\n2. **Task Management:**\n - Update status in real-time\n - Mark complete IMMEDIATELY after finishing\n - Only ONE task in_progress at a time\n - Complete current tasks before starting new ones\n - Use merge=true for incremental updates. Use merge=false only for the first todo list or when intentionally replacing the entire list and including every existing todo id.\n\n3. **Task Breakdown:**\n - Create specific, actionable items\n - Break complex tasks into manageable steps\n - Use clear, descriptive names\n\n4. **Parallel Todo Writes:**\n - Prefer creating the first todo as in_progress\n - Start working on todos by using tool
|
||
|
|
"name": "TodoWrite",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"merge": {
|
||
|
|
"description": "Whether to merge the todos with the existing todos. If true, the todos will be merged into the existing todos based on the id field. Use true for normal incremental updates, marking items complete, adding follow-ups, or changing the current in-progress item. If false, the new todos replace the entire list and must include every existing todo id once a list already exists.",
|
||
|
|
"type": "boolean"
|
||
|
|
},
|
||
|
|
"todos": {
|
||
|
|
"description": "Array of TODO items to update or create",
|
||
|
|
"items": {
|
||
|
|
"properties": {
|
||
|
|
"content": {
|
||
|
|
"description": "The description/content of the todo item. For merge=true updates, omit content when it is unchanged. New todos and merge=false replacements must include content.",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"id": {
|
||
|
|
"description": "Unique identifier for the TODO item",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"status": {
|
||
|
|
"description": "The current status of the TODO item. For merge=true updates, omit status when it is unchanged.",
|
||
|
|
"enum": [
|
||
|
|
"pending",
|
||
|
|
"in_progress",
|
||
|
|
"completed",
|
||
|
|
"cancelled"
|
||
|
|
],
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"id"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
},
|
||
|
|
"minItems": 1,
|
||
|
|
"type": "array"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"todos",
|
||
|
|
"merge"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Read and display linter errors from the current workspace. You can provide paths to specific files or directories, or omit the argument to get diagnostics for all files.\n\n- If a file path is provided, returns diagnostics for that file only\n- If a directory path is provided, returns diagnostics for all files within that directory\n- If no path is provided, returns diagnostics for all files in the workspace\n- This tool can return linter errors that were already present before your edits, so avoid calling it with a very wide scope of files\n- NEVER call this tool on a file unless you've edited it or are about to edit it",
|
||
|
|
"name": "ReadLints",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"paths": {
|
||
|
|
"description": "Optional. An array of paths to files or directories to read linter errors for. You can use either relative paths in the workspace or absolute paths. If provided, returns diagnostics for the specified files/directories only. If not provided, returns diagnostics for all files in the workspace.",
|
||
|
|
"items": {
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"type": "array"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Search the web for real-time information about any topic. Returns summarized information from search results and relevant URLs.\n\nUse this tool when you need up-to-date information that might not be available or correct in your training data, or when you need to verify current facts.\nThis includes queries about:\n- Libraries, frameworks, and tools whose APIs, best practices, or usage instructions are frequently updated. (\"How do I run Postgres in a container?\")\n- Current events or technology news. (\"Which AI model is best for coding?\")\n- Informational queries similar to what you might Google (\"kubernetes operator for mysql\")\n\nIMPORTANT - Use the correct year in search queries:\n- Today's date is 2026-03-15. You MUST use this year when searching for recent information, documentation, or current events.\n- Example: If today is 2026-07-15 and the user asks for \"latest React docs\", search for \"React documentation 2026\", NOT \"React documentation 2025\"",
|
||
|
|
"name": "WebSearch",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"explanation": {
|
||
|
|
"description": "One sentence explanation as to why this tool is being used, and how it contributes to the goal.",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"search_term": {
|
||
|
|
"description": "The search term to look up on the web. Be specific and include relevant keywords for better results. For technical queries, include version numbers or dates if relevant.",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"search_term"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Fetch content from a specified URL and return its contents in a readable markdown format. Use this tool when you need to retrieve and analyze webpage content.\n\n- The URL must be a fully-formed, valid URL.\n- This tool is read-only and will not work for requests intended to have side effects.\n- This fetch tries to return live public web results.\n- Authentication is not supported, and an error will be returned if the URL requires authentication.\n- If the URL is returning a non-200 status code, e.g. 404, the tool will not return the content and will instead return an error message.\n- This fetch uses a public-web-only backend fetch policy. Localhost, private IPs, and link-local addresses will not work.\n- This tool does not support fetching binary content, e.g. media or PDFs.\n- For static assets and non-webpage URLs, use the `Shell` tool instead.\n",
|
||
|
|
"name": "WebFetch",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"url": {
|
||
|
|
"description": "The URL to fetch. The content will be converted to a readable markdown format.",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"url"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Collect structured multiple-choice answers from the user.\nProvide one or more questions with options, and set allow_multiple when multi-select is appropriate.\n\nUse this tool when you need to gather specific information from the user through a structured question format.\nEach question should have:\n- A unique id (used to match answers)\n- A clear prompt/question text\n- At least 2 options for the user to choose from\n- An optional allow_multiple flag (defaults to false for single-select)\nBy default, the tool will present the questions to the user and wait for their responses before continuing.",
|
||
|
|
"name": "AskQuestion",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"questions": {
|
||
|
|
"description": "Array of questions to present to the user (minimum 1 required)",
|
||
|
|
"items": {
|
||
|
|
"properties": {
|
||
|
|
"allow_multiple": {
|
||
|
|
"description": "If true, user can select multiple options. Defaults to false.",
|
||
|
|
"type": "boolean"
|
||
|
|
},
|
||
|
|
"id": {
|
||
|
|
"description": "Unique identifier for this question",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"options": {
|
||
|
|
"description": "Array of answer options (minimum 2 required)",
|
||
|
|
"items": {
|
||
|
|
"properties": {
|
||
|
|
"id": {
|
||
|
|
"description": "Unique identifier for this option",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"label": {
|
||
|
|
"description": "Display text for this option",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"id",
|
||
|
|
"label"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
},
|
||
|
|
"minItems": 2,
|
||
|
|
"type": "array"
|
||
|
|
},
|
||
|
|
"prompt": {
|
||
|
|
"description": "The question text to display to the user",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"id",
|
||
|
|
"prompt",
|
||
|
|
"options"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
},
|
||
|
|
"minItems": 1,
|
||
|
|
"type": "array"
|
||
|
|
},
|
||
|
|
"title": {
|
||
|
|
"description": "Optional title for the questions form",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"questions"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Use this tool to create or revise a concise plan for accomplishing the user's request. This tool should be called at the end of the planning phase to finalize and store the plan.\n\nThe plan you create should be properly formatted in markdown, using appropriate sections and headers. The plan should be very concise and actionable, providing the minimum amount of detail for the user to understand and action the plan. It may be helpful to identify the most important couple files you will change, and existing code you will leverage. Cite specific file paths and essential snippets of code. IMPORTANT: Do NOT use markdown tables in plan content (they cannot be rendered for the user); use bullet lists instead. The first line MUST BE A TITLE for the plan formatted as a level 1 markdown heading.\n\nTASK ORGANIZATION:\n\nUse 'todos' for organizing implementation tasks:\n- Each todo should be a clear, specific, and actionable task\n- Each todo needs a unique ID (e.g., \"setup-auth\") and descriptive content\n- If the plan is simple, provide just a few high-level todos or none at all\n\nUPDATING THE PLAN:\n- The plan file URI will be returned in the tool result\n- If a current plan already exists, call this tool with the complete revised plan and omit the name field\n- Only the first CreatePlan call may include name; later calls must not include name and must not use name to rename or create a separate plan\n- If the user asks for a separate new plan while a current plan exists, explain the limitation or ask how to proceed before calling CreatePlan again\n\nAdditional guidelines:\n- Avoid asking clarifying questions in the plan itself. Ask them before calling this tool. Present these to the user using the AskQuestion tool.\n- Todos help break down complex plans into manageable, trackable tasks\n- Focus on high-level meaningful decisions rather than low-level implementation details\n- A good plan is glanceable, not a wall of text.",
|
||
|
|
"name": "CreatePlan",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"name": {
|
||
|
|
"description": "A short 3-4 word name for the plan. IMPORTANT: Provide this only on the first CreatePlan call when no current plan exists. If a current plan already exists, omit this field entirely; do not use it to rename or create a separate plan.",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"overview": {
|
||
|
|
"description": "A 1-2 sentence high-level description of the plan that summarizes what will be accomplished",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"plan": {
|
||
|
|
"description": "A detailed, concrete plan for accomplishing the user's request",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"todos": {
|
||
|
|
"description": "Array of implementation todos",
|
||
|
|
"items": {
|
||
|
|
"properties": {
|
||
|
|
"content": {
|
||
|
|
"description": "Description of the todo task",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"id": {
|
||
|
|
"description": "Unique identifier for the todo",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"id",
|
||
|
|
"content"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
},
|
||
|
|
"type": "array"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Launch a new agent to handle complex, multi-step tasks autonomously.\n\nPLAN MODE PARALLEL INVESTIGATION POLICY:\nUse Task in plan mode as a parallel investigation tool, not as a replacement for your own reasoning. For any non-trivial implementation plan, first do a quick reconnaissance yourself, then launch 2-4 parallel subagents, usually with subagent_type=\"explore\", to investigate distinct angles, and then synthesize their findings yourself before calling CreatePlan.\n\nLaunch multiple explore subagents when any of these are true:\n- The request spans backend/frontend/protocol/storage/build or multiple directories.\n- The current behavior is unclear and needs tracing.\n- There are multiple possible implementation strategies.\n- The change may affect existing behavior, compatibility, history, state projection, prompt compilation, tool protocols, persistence, or UI state.\n- The user asks for a plan for a feature, bugfix, refactor, architecture change, or investigation.\n\nAvoid exactly one subagent for broad tasks:\n- If only one investigation track exists, investigate it yourself with the direct tools.\n- If the task is broad enough for subagents, split it into at least two independent tracks and launch them concurrently.\n- Do not use a single subagent as a symbolic substitute for real parallel investigation.\n\nGood parallel split examples:\n- Protocol path vs state/history projection vs prompt/tool schema.\n- Frontend UI behavior vs backend API behavior vs persisted data model.\n- Current implementation vs installed-client/runtime behavior vs test/build impact.\n\nIf the query is narrow, localized, or can be resolved by reading 1-2 files directly, you should NOT use the Task tool and instead investigate directly using the other tools available to you.\n\nThe Task tool launches specialized subagents (subprocesses) that autonomously handle complex tasks. Each subagent_type has specific capabilities and tools available to it.\n\nWhen using the Task tool, you must specify a subagent_type parameter to select which agent type to use.\n\nVERY IMPORTANT: When broadly exploring the codebase to gather context for a large task, use 2-4 parallel Task calls with subagent_type=\"explore\" instead of only running searches directly.\n\nExamples:\n- user: \"Where is the ClientError class defined?\" assistant: [Uses Grep directly - this is a needle query for a specific class]\n- user: \"Run this query using my database API\" assistant: [Calls the MCP directly - this is not a broad exploration task]\n- user: \"What is the codebase structure?\" assistant: [Uses multiple parallel Task calls with subagent_type=\"explore\" for different directories or concerns]\n\nIf it is possible to explore different areas of the codebase in parallel, you should launch multiple agents concurrently.\n\nWhen NOT to use the Task tool:\n- Simple, single or few-step tasks that can be performed by a single agent (using parallel or sequential tool calls) -- just call the tools directly instead.\n- For example:\n - If you want to read a specific file path, use the Read or Glob tool instead of the Task tool, to find the match more quickly\n - If you are searching for code within a specific file or set of 2-3 files, use the Read tool instead of the Task tool, to find the match more quickly\n - If you are searching for a specific class definition like \"class Foo\", use the Glob tool instead, to find the match more quickly\n\nUsage notes:\n- Always include a short description (3-5 words) summarizing what the agent will do\n- In plan mode, for complex discovery tasks, prefer 2-4 concurrent agents before CreatePlan. IMPORTANT: DO NOT launch more than 4 agents concurrently.\n- For each explore subagent, specify: scope, the concrete question to answer, expected output with file/function references, and a readonly investigation boundary.\n- Make each subagent investigate a different angle. Avoid overlapping assignments unless you intentionally need independent confirmation of a risky point.\n- When the agent is done, it will return a single
|
||
|
|
"name": "Task",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"attachments": {
|
||
|
|
"description": "Optional array of file paths to videos to pass to video-review subagents. Files are read and attached to the subagent's context. Supports video formats (mp4, webm) for Gemini models.",
|
||
|
|
"items": {
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"type": "array"
|
||
|
|
},
|
||
|
|
"description": {
|
||
|
|
"description": "A short (3-5 word) description of the task",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"model": {
|
||
|
|
"description": "Optional model to use for this agent. If not specified, inherits from parent. Prefer fast for quick, straightforward tasks to minimize cost and latency. Only select a different model when the task specifically benefits from it (e.g., deep reasoning, high-quality code review, multimodal input)",
|
||
|
|
"enum": [
|
||
|
|
"fast"
|
||
|
|
],
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"prompt": {
|
||
|
|
"description": "The task for the agent to perform",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"readonly": {
|
||
|
|
"description": "If true, the subagent will run in readonly mode (\"Ask mode\") with restricted write operations and no MCP access.",
|
||
|
|
"type": "boolean"
|
||
|
|
},
|
||
|
|
"resume": {
|
||
|
|
"description": "Optional agent ID to resume from. If provided, sends a follow-up message to the agent when its turn is complete.",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"subagent_type": {
|
||
|
|
"description": "Subagent type to use for this task. Must be one of: generalPurpose, explore, shell, browser-use.",
|
||
|
|
"enum": [
|
||
|
|
"generalPurpose",
|
||
|
|
"explore",
|
||
|
|
"shell",
|
||
|
|
"browser-use"
|
||
|
|
],
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"description",
|
||
|
|
"prompt"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Reads a specific resource from an MCP server, identified by server name and resource URI. Optionally, set downloadPath (relative to the workspace) to save the resource to disk; when set, the resource will be downloaded and not returned to the model.",
|
||
|
|
"name": "FetchMcpResource",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"downloadPath": {
|
||
|
|
"description": "Optional relative path in the workspace to save the resource to. When set, the resource is written to disk and is not returned to the model.",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"server": {
|
||
|
|
"description": "The MCP server identifier",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"uri": {
|
||
|
|
"description": "The resource URI to read",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"server",
|
||
|
|
"uri"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
},
|
||
|
|
{
|
||
|
|
"function": {
|
||
|
|
"description": "Call an MCP tool by server identifier and tool name with arbitrary JSON arguments. IMPORTANT: Always read the tool's schema/descriptor BEFORE calling to ensure correct parameters.\n\nExample:\n{\n \"server\": \"my-mcp-server\",\n \"toolName\": \"search\",\n \"arguments\": { \"query\": \"example\", \"limit\": 10 }\n}",
|
||
|
|
"name": "CallMcpTool",
|
||
|
|
"parameters": {
|
||
|
|
"properties": {
|
||
|
|
"arguments": {
|
||
|
|
"description": "Arguments to pass to the MCP tool, as described in the tool descriptor.",
|
||
|
|
"type": "object"
|
||
|
|
},
|
||
|
|
"server": {
|
||
|
|
"description": "Identifier of the MCP server hosting the tool.",
|
||
|
|
"type": "string"
|
||
|
|
},
|
||
|
|
"toolName": {
|
||
|
|
"description": "Name of the MCP tool to invoke.",
|
||
|
|
"type": "string"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"required": [
|
||
|
|
"server",
|
||
|
|
"toolName"
|
||
|
|
],
|
||
|
|
"type": "object"
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"type": "function"
|
||
|
|
}
|
||
|
|
]
|