Dolly Agent Tools
Dolly’s tools are registered via ADK’s functiontool.New and defined in internal/dolly/agent/. Dolly focuses on project management — Jira ticket lifecycle, Confluence and Google Drive knowledge, team settings, and epic decomposition.
Core Jira Tools
Section titled “Core Jira Tools”create_jira_ticket
Section titled “create_jira_ticket”Creates a Jira ticket. Requires investment_category (one of: “Feature Development”, “Bug Fixing”, “Keeping the Lights On”, “Incidents”). Returns the issue key and URL.
update_jira_ticket
Section titled “update_jira_ticket”Updates an existing ticket. All fields except issue_key are optional.
get_jira_ticket
Section titled “get_jira_ticket”Gets full details by issue key. Returns summary, description, status, labels, comments, and links.
search_jira
Section titled “search_jira”Searches using JQL. Returns matching issues with key, summary, status, type, and assignee.
Response Tools
Section titled “Response Tools”respond_in_slack
Section titled “respond_in_slack”Posts to the Slack thread associated with the current session. Uses Slack mrkdwn formatting.
respond_in_jira
Section titled “respond_in_jira”Posts a comment on the associated Jira ticket. Supports markdown.
Status and Reporting
Section titled “Status and Reporting”get_epic_status
Section titled “get_epic_status”Gets the status summary of an epic and all child issues, grouped by status.
generate_jira_report
Section titled “generate_jira_report”Generates a progress report for a project or board within a time period. Optionally filter by assignee.
Knowledge Sources
Section titled “Knowledge Sources”search_confluence
Section titled “search_confluence”Searches Confluence pages by text query, optionally filtered by space key.
read_confluence_page
Section titled “read_confluence_page”Reads a Confluence page by ID or URL. Returns content as markdown.
search_google_drive
Section titled “search_google_drive”Searches Google Drive for files matching a query. Returns names, IDs, types, and links.
read_google_doc
Section titled “read_google_doc”Reads a Google Doc or Sheet by ID or URL. Returns content as markdown. Auto-detects file type.
Team Settings
Section titled “Team Settings”get_team_settings
Section titled “get_team_settings”Gets the team’s Jira project, acceptance criteria format, labels, template, and target repos.
update_team_settings
Section titled “update_team_settings”Creates or updates team settings. Only team_name is required; all other fields are optional.
list_team_settings
Section titled “list_team_settings”Lists all configured teams and their settings.
User Memory
Section titled “User Memory”recall_user_memory
Section titled “recall_user_memory”Recalls saved notes about a Slack user — their team, role, preferences, and past interactions.
update_user_memory
Section titled “update_user_memory”Saves or updates memory about a user. Concise markdown, under 2000 characters.
Decomposition
Section titled “Decomposition”propose_decomposition
Section titled “propose_decomposition”Proposes an epic breakdown as individual tickets and posts an approval UI in Slack with Approve/Reject buttons. Tickets use Fibonacci story points, with 3-8 tickets per decomposition.
bulk_create_tickets
Section titled “bulk_create_tickets”Creates all approved tickets in Jira, links them sequentially, and assigns them under the parent epic.
Handoffs
Section titled “Handoffs”handoff_to_buck
Section titled “handoff_to_buck”Assigns the ticket to Buck, adds the ready-for-buck label, and tags @Buck in Slack. Use when the ticket is fully defined with clear acceptance criteria.
handoff_to_pearl
Section titled “handoff_to_pearl”Adds the needs-design label and tags @Pearl in Slack. Use when the ticket needs design work before implementation.
approve_pearl_design
Section titled “approve_pearl_design”Downloads the design screenshot, attaches it to the Jira ticket, adds the design-approved label, removes needs-design, and hands off to Buck.
request_pearl_changes
Section titled “request_pearl_changes”Tags Pearl in Slack with design feedback requesting revisions.