DevBoy Tools Reference
Auto-generated by
devboy tools docsfrombase_tool_definitions()and the static provider catalog. Do not edit by hand — re-run the command to refresh.
DevBoy Tools v0.29.0 ships 54 provider-backed tools across 7 categories, 11 always-on context tools, and 7 providers.
Provider Support Matrix
Legend: ✅ supported · ⚠️ conditional (see notes) · — not applicable.
Conditional support
- Jira → Jira Structure: requires the Structure plugin to be installed and accessible.
Issue Tracker Tools
Providers: GitHub, GitLab, ClickUp, Jira.
add_issue_comment
Add a comment to an issue with optional file attachments (ClickUp only).
assign_to_sprint
Move one or more issues onto a Jira sprint. Pair with get_board_sprints to look up the numeric sprintId. Issues already on a sprint are silently moved.
create_issue
Create a new issue in the configured provider.
delete_asset
Delete a file attachment from an issue. Not all providers support this — check asset_capabilities first.
download_asset
Download a file attachment to local cache. Returns local file path when cache is available, base64-encoded content as fallback.
get_assets
List file attachments for an issue or merge request.
get_available_statuses
Get available statuses for the issue tracker.
No parameters.
get_board_sprints
List sprints visible on a Jira agile board. Use to discover the numeric sprintId accepted by create_issue / update_issue and assign_to_sprint. Returns name, state (active/future/closed), planned start/end, and goal — enough for the agent to pick the right sprint without a follow-up call.
get_custom_fields
List custom fields available on the issue tracker, with their id, name, and field type. Use to discover the customfield_* id of a Jira instance — names like Epic Link, Sprint, Epic Name map to different ids on every deployment. Pair with customFields: { "<id>": <value> } on create_issue / update_issue for fields not yet exposed as first-class params.
get_issue
Get a single issue by key with optional comments and relations.
get_issue_comments
Get comments for an issue.
get_issue_relations
Get relations for an issue (parent, subtasks, linked issues).
get_issues
Get issues from configured provider. Returns a list with filters.
get_users
Get users from the issue tracker (Jira). Search by name, project, or ID.
link_issues
Link two issues together (blocks, relates_to, etc.).
list_project_versions
List Jira project versions / fixVersion targets (releases). Returns rich per-version payload (description, dates, released/archived flags, optional issue counts). Default filter hides archived versions and limits to 20 most recent (unreleased first, then released by releaseDate desc). For issue-level details on a release, follow up with get_issues and a JQL nativeQuery such as fixVersion = "<name>" — there is no per-id get tool by design.
unlink_issues
Remove a link between two issues.
update_issue
Update an existing issue. Only provided fields will be changed.
upload_asset
Upload a file attachment to an issue. Returns the download URL.
upsert_project_version
Create or partially update a Jira project version, keyed by (project, name). If a version with this name exists, fields you supply are updated and unspecified fields are preserved. If not, a new version is created. Useful for writing release notes (description) or closing a release (released: true, releaseDate).
Git Repository Tools
Providers: GitHub, GitLab.
create_merge_request
Create a new merge request (GitLab) or pull request (GitHub).
create_merge_request_comment
Add a comment to a merge request. Can be general or inline code review.
get_job_logs
Get CI/CD job logs. Modes: smart (auto errors), search (pattern), paginated, full.
get_merge_request
Get a single merge request by key (e.g., 'pr#123', 'mr#456').
get_merge_request_diffs
Get file diffs for a merge request.
get_merge_request_discussions
Get discussions/review comments for a merge request with code positions.
get_merge_requests
Get merge requests / pull requests from configured provider.
get_pipeline
Get CI/CD pipeline status for branch or MR/PR with job details.
update_merge_request
Update a merge request / pull request (title, description, state, labels, draft).
Epics Tools
Providers: ClickUp.
create_epic
Create a new epic.
get_epics
Get epics (high-level tasks) from the issue tracker.
update_epic
Update an existing epic.
Meeting Notes Tools
Providers: Fireflies.
get_meeting_notes
Get meeting notes and transcripts with optional filters (date range, participants, host).
get_meeting_transcript
Get the full transcript for a meeting. Returns speaker-attributed sentences with timestamps.
search_meeting_notes
Search across meetings by keywords, topics, or action items, with optional filters (date range, participants, host).
Knowledge Base Tools
Providers: Confluence.
create_knowledge_base_page
Create a knowledge base page in a space.
get_knowledge_base_page
Get a knowledge base page with content, labels, and ancestors.
get_knowledge_base_spaces
List available knowledge base spaces.
No parameters.
list_knowledge_base_pages
List pages in a knowledge base space with pagination.
search_knowledge_base
Search knowledge base pages across spaces using free text or provider-native syntax such as CQL.
update_knowledge_base_page
Update a knowledge base page title, content, metadata, or labels.
Messenger Tools
Providers: Slack.
get_chat_messages
Get message history for a chat or fetch replies for a specific thread.
get_messenger_chats
List available messenger chats, channels, groups, or direct messages.
search_chat_messages
Search messages across accessible chats or within a specific chat.
send_message
Send a message to a chat or as a threaded reply.
Jira Structure Tools
Providers: Jira (conditional).
add_structure_rows
Add items (Jira issues or folders) to a Structure. Specify position with under (parent row) and/or after (sibling row). Use forestVersion for optimistic concurrency.
create_structure
Create a new Jira Structure. After creation, use add_structure_rows to populate and save_structure_view to configure columns.
get_structure_forest
Get the hierarchy tree of a Jira Structure. Returns nested tree with rowId, itemId (Jira issue key), itemType, and children. Supports pagination for large structures.
get_structure_values
Read column values (including Expr formulas like SUM, PROGRESS, COUNT) for specific rows in a Jira Structure. Values are computed server-side.
get_structure_views
Get views for a Jira Structure. Without viewId: lists all views. With viewId: returns full view configuration (columns, grouping, sorting, filter).
get_structures
List all available Jira Structures. Returns structure ID, name, and description. Requires Jira with Structure plugin.
No parameters.
move_structure_rows
Move rows within a Jira Structure hierarchy. Specify new position with under (new parent) and/or after (sibling).
remove_structure_row
Remove a row from a Jira Structure. Only removes from the structure hierarchy — the underlying Jira issue is NOT deleted.
save_structure_view
Create or update a Jira Structure view. Views define column layout (fields and formulas), grouping, sorting, and filters. Omit id to create new.
Context Management Tools
Always-on tools attached to every tools/list response, independent of which providers are configured. They let the agent inspect or switch the active context.
list_contexts
List configured contexts and indicate the active context.
No parameters.
use_context
Switch active context at runtime.
get_current_context
Get current active context name.
No parameters.
secrets_list
List secrets the active context's manifest declares. Returns metadata only — values are never included. Optional filter narrows by path substring, scope, status, or whether to include framework-internal paths.
secrets_describe
Describe one secret by ADR-020 path. Returns the same metadata fields as secrets_list plus description, retrieval URL, rotation method, last rotated date, rotation cadence, and pattern ID. The value is never returned.
secrets_request_provision
Open the provisioning UI dialog for the given ADR-020 path. The dialog hands the user-entered value directly to the local daemon — the agent never sees it. Returns a request_id that can be polled with secrets_poll_status. Mode defaults to provision; pass rotation to surface the destructive-confirm checkbox. Pending requests expire 5 minutes after issuance.
secrets_poll_status
Poll a provisioning or rotation request issued by secrets_request_provision / secrets_request_rotation. Returns one of pending / ok / cancelled / expired / failed plus the request's age in seconds and the path it was opened for.
secrets_request_rotation
Open the rotation UI dialog for the given ADR-020 path. Same lifecycle as secrets_request_provision but the dialog surfaces the destructive-confirm checkbox so the user explicitly acknowledges that the existing value is being overwritten. Reuses secrets_poll_status for status. Pending requests expire 5 minutes after issuance.
secrets_request_use_approval
Open the use-approval dialog for an ADR-020 path whose approve_on_use is set to session or per-call. The agent supplies a short human-facing reason that the dialog renders verbatim alongside the path; the user picks once, session, or denied. Returns a request_id to poll via secrets_poll_status. Pending requests expire 5 minutes after issuance; ttl_seconds may shorten the window but never extend it. The agent never sees the secret — only whether the user approved its use.
secrets_propose_metadata
Suggest metadata edits for an existing ADR-020 path. The dialog renders the manifest's current values as the diff baseline (read straight from the index — agent strings never replace trusted fields, mitigating prompt-injection). The user picks which proposed fields to accept. Reuses secrets_poll_status for status. Pending requests expire 5 minutes after issuance.
secrets_propose_new_path
Suggest registering a new secret at the given path. The dialog opens with the suggested path editable and the proposed metadata visible in a diff column for review. The user has the final say on the path and the metadata that lands in the manifest. Reuses secrets_poll_status for status. Pending requests expire 5 minutes after issuance.