Built-in tools give agents a unified, provider-agnostic interface for interacting with your connected systems. You write agent instructions using generic language (“create a ticket”, “open a pull request”, “read the file”) and Overcut routes each operation to the correct provider based on your workspace integrations.
Provider-agnostic by design. A tool like Create Ticket works across Jira, Linear, ClickUp, GitHub Issues, and GitLab Issues without any changes to your agent instructions. Overcut handles the provider-specific details automatically.
Built-in tools work through your connected workspace integrations for supported providers. If you are deciding how to connect a system, start with the Integrations overview. If you need external tools or third-party systems beyond native integrations, use MCP Servers. read_file to inspect the config before making changes”.
Beyond the tools listed here, agents also receive scratchpad tools and memory tools automatically. These are injected at runtime and are not part of the per-agent tool selection.
File System
File system tools operate on repositories that have been cloned via the git.clone action.
| Tool | Name | Description |
|---|
| Read File | read_file | Reads the content of a file. |
| Write File | write_file | Creates or overwrites a file with new content. |
| Edit File | edit_file | Applies targeted edits to an existing file without rewriting it entirely. |
| Append File | append_file | Appends content to the end of an existing file. |
| Delete File | delete_file | Deletes a file from the repository. |
| Create Directory | create_directory | Creates a new directory in the repository. |
| List Directory | list_dir | Lists the files and directories at a given path. |
Code Utilities
Code utility tools help agents understand and navigate codebases. They operate on cloned repositories.
| Tool | Name | Description |
|---|
| Search Code | code_search | Searches for an exact string or pattern across all files in the repository. |
| Semantic Code Search | semantic_code_search | Searches code by meaning rather than exact text, useful for finding relevant logic even when the wording varies. Requires repository indexing to be enabled for the repository. |
| Execute Terminal Commands | run_terminal_cmd | Runs terminal commands in the cloned repository (e.g., build scripts, test runners, linters). |
| Explore Codebase | explore_codebase | Runs an internal exploration sub-agent to deeply analyze a specific aspect of the codebase, returning a structured summary. Useful for understanding unfamiliar areas of a large repository. |
Tickets and Issues
Ticket tools connect to your issue tracking integrations. The same instructions work across Jira, Linear, ClickUp, GitHub Issues, GitLab Issues, and Azure DevOps: the agent uses generic ticket language and Overcut maps it to the active provider.
| Tool | Name | Description |
|---|
| Create Ticket | create_ticket | Creates a new ticket or issue with title, description, and metadata. |
| Update Ticket | update_ticket | Updates an existing ticket’s fields (title, description, status, assignee, etc.). |
| Read Ticket | read_ticket | Reads the full details of a specific ticket, including linked relationships when the provider exposes them. |
| List Tickets | list_tickets | Lists tickets matching a query or filter (project, status, assignee, label, etc.). |
| Add Comment to Ticket | add_comment_to_ticket | Adds a new comment to a ticket. |
| Update Comment on Ticket | update_comment_on_ticket | Edits an existing comment on a ticket. |
| Get Ticket Attachments | get_ticket_attachments | Retrieves file attachments from a ticket. |
| Link Tickets | link_tickets | Creates a typed link between two tickets on the same provider (for example, blocks or relates to). |
| Unlink Tickets | unlink_tickets | Removes an existing link from a ticket. |
| Get Ticket Metadata | get_ticket_metadata | Discovers provider-defined options such as available relationship (link) types, labels, and statuses before creating a link. |
Linked ticket relationships
On supported ticket providers, agents can work with linked relationships between tickets as part of normal ticket operations. This helps agents connect related bugs, follow-up work, blockers, and dependencies without leaving Overcut.
Agents can:
- Create linked relationships between tickets on providers that support them
- Remove linked relationships when they are no longer accurate
- Read existing linked relationships from tickets and use them as context when reasoning about related work
- Inspect the relationship types a provider offers before attempting to create a link
Relationship types are provider-specific. Overcut does not apply one universal set of relationship names across every integration. Before creating a linked relationship, agents can inspect the available relationship types for the connected provider and use one that matches that provider’s rules.
Cross-project linking also depends on the connected provider. If the provider allows tickets in different projects, spaces, or teams to be linked, agents can create those links through Overcut. If the provider restricts linking to the same project or repository, Overcut follows that behavior.
See the integration overview for the full ticket provider list, then review your provider page for setup details and support expectations such as project scope, status behavior, and link availability. Provider support expectations
Typed ticket relationships are available only on providers that expose them through Overcut’s native ticketing surface. Support differs by integration:
- Jira: supports provider-defined relationship types, linked ticket reads, and cross-project linking when Jira allows it
- Linear: supports provider-defined relationship types and linked ticket reads
- ClickUp: supports link creation, link removal, and linked ticket reads. ClickUp uses a single provider-defined link option rather than a broader set of typed relationships
- GitLab: supports provider-defined relationship types, linked ticket reads, and cross-project linking when GitLab allows it
- Azure DevOps: supports provider-defined relationship types, linked ticket reads, and cross-project linking when Azure DevOps allows it
- GitHub Issues: does not support typed ticket links through Overcut’s native ticketing surface
- Bitbucket: does not support typed ticket links through Overcut’s native ticketing surface
For provider-specific guidance, see Jira, Linear, ClickUp, GitLab, Azure DevOps, GitHub, and Bitbucket.
Pull Requests
Pull request tools connect to your source control integrations. They work across GitHub, GitLab, Bitbucket, and Azure DevOps through the same unified interface.
| Tool | Name | Description |
|---|
| Create Pull Request | create_pull_request | Opens a new pull request with title, description, and branch information. |
| Read Pull Request | read_pull_request | Reads the full details of a pull request including description, status, and labels. |
| Update Pull Request | update_pull_request | Updates a pull request’s title, description, labels, or other metadata. |
| List Pull Requests | list_pull_requests | Lists pull requests matching a filter (status, author, branch, label, etc.). |
| Merge Pull Request | merge_pull_request | Merges an approved pull request. |
| Close Pull Request | close_pull_request | Closes a pull request without merging. |
| Add Comment to Pull Request | add_comment_to_pull_request | Posts a general comment on a pull request. |
| Update Comment on Pull Request | update_comment_on_pull_request | Edits an existing general comment on a pull request. |
| Get Pull Request Attachments | get_pull_request_attachments | Retrieves file attachments from a pull request. |
Code Review
Code review tools enable structured, line-level review feedback on pull requests. They are supported on GitHub, GitLab, Bitbucket, and Azure DevOps.
| Tool | Name | Description |
|---|
| Get Pull Request Diff | get_pull_request_diff | Fetches the full code diff for a pull request. |
| Get Pull Request Diff Line Numbers | get_pull_request_diff_line_numbers | Fetches the diff with explicit line number annotations, used for precise inline review placement. |
| Add Review Comment | add_pull_request_review_thread | Adds an inline review comment on a specific line or hunk in a pull request diff. |
| Reply to Review Comment | add_pull_request_review_thread_reply | Replies to an existing inline review thread. |
| Submit Review | submit_review | Submits a completed review with an overall verdict (approve, request changes, or comment). |
CI/CD
CI/CD tools let agents monitor and interact with your continuous integration pipelines. They work with GitHub Actions, GitLab CI, Bitbucket Pipelines, and Azure Pipelines.
| Tool | Name | Description |
|---|
| List PR CI Runs | list_pr_ci_runs | Lists all CI workflow runs associated with a pull request. |
| Get CI Run Details | get_ci_run_details | Retrieves details about a specific CI run: status, steps, timing. |
| Get CI Run Logs | get_ci_run_logs | Fetches the full log output for a CI run. |
| Get CI Job Logs | get_ci_job_logs | Fetches the log output for a specific job within a CI run. |
| Retry CI Workflow | retry_ci_workflow | Triggers a retry of a failed CI workflow run. |
Chat Channels
Chat channel tools let agents participate in conversations in a registered Slack channel where a workflow was triggered. They are assigned per agent and only act in channels that are registered to the project: see Slack integration.
| Tool | Name | Description |
|---|
| Post Channel Message | post_channel_message | Posts a message in the registered channel, either in the channel itself or as a thread reply. |
| Read Channel Messages | read_channel_messages | Reads recent messages from the channel so the agent can understand context before responding. |
| Edit Channel Message | edit_channel_message | Edits a message the agent (or workflow) previously posted in the channel. |
| Add Reaction | add_channel_message_reaction | Adds an emoji reaction to a message in the channel. |
| Remove Reaction | remove_channel_message_reaction | Removes an emoji reaction the agent previously added. |
The following tools are automatically available to every agent regardless of which tools are selected. They cannot be added or removed manually.
| Tool | Name | Description |
|---|
| Write Scratchpad | write_scratchpad | Creates or overwrites a named scratchpad. |
| Append Scratchpad | append_scratchpad | Appends content to a named scratchpad. |
| Read Scratchpad | read_scratchpad | Reads the content of a named scratchpad. |
| List Scratchpads | list_scratchpads | Lists all scratchpad names in the current run. |
| Memory Write | memory_write | Writes a persistent memory entry, available in future runs. |
| Memory Recall | memory_recall | Fetches the full content of a memory by ID. Agents see memory titles injected into their prompt and call memory_recall to pull in the ones that look relevant. Calls to this tool count toward the memory’s use count, which feeds back into how the memory is weighted over time. |
| Update Status | update_status | Sends a real-time status update visible in the Overcut UI during execution. |
In addition to the built-in tools above, you can connect MCP Servers to give agents access to external tools: web search, databases, third-party APIs, and more. MCP extends agent capabilities with third-party systems and custom tools. For first-class providers that Overcut supports through workspace integrations, MCP is a supplemental or fallback option rather than a replacement for the native connection path. MCP tools appear alongside built-in tools in the agent tool list and are configured per agent in the MCP Servers section. Browse pre-configured servers in the MCP Catalog. 
