## Summary We've accumulated 85+ tools across our AI platform. This sprawling catalog degrades performance and usability. Agents select wrong tools during execution, users building custom agents and flows can't find what they need, and the sheer volume creates maintenance burden and confusion. ##### MVP Scope Complete audit of existing tools, consolidate the existing catalog while establishing a documented framework for future tool development. This includes migrating DAP to MCP tools (eliminating duplication), building composite tools that handle multi-step workflows efficiently, exploring supertool approaches for flexibility, and maintaining narrow purpose-built tools where appropriate. --- <details> <summary>Additional details</summary> ## Description We've accumulated 85+ tools across our AI platform. This sprawling catalog degrades performance and usability. Agents select wrong tools during execution, users building custom agents and flows can't find what they need, and the sheer volume creates maintenance burden and confusion. To resolve this, we'll audit and consolidate the existing catalog while establishing a documented framework for future tool development. This includes migrating DAP to MCP tools (eliminating duplication), building composite tools that handle multi-step workflows efficiently, exploring supertool approaches for flexibility, and maintaining narrow purpose-built tools where appropriate. The result: a curated, comprehensive catalog of high-quality tools that agents can navigate effectively and teams can maintain sustainably. ## Scope ### What's included - Complete audit of 85+ existing tools - Consolidation plan: identify overlap, underused tools, merge opportunities - Migration of high-priority legacy DAP tools → MCP tooling - Tool quality standards (documentation, testing, error handling, performance benchmarks) - Generic/supertool exploration ### What's not included - Advanced workflow features - Tool registry within AI Catalog (providing creators with better insight into tool capabilities) ## UX Outcome - Agents select the right tool faster (reduced confusion from tool proliferation) - Tools work reliably (consistent quality standards) - Creators find tools easier to discover </details> ## Migration mapping (current GitLab MCP server → consolidated surface) The diagram below maps only the tools **currently in the GitLab MCP server** (22 tools) onto the consolidated target surface. ```mermaid flowchart LR subgraph SRC["Current GitLab MCP server"] s_ci["gitlab_create_issue"] s_gi["gitlab_get_issue"] s_gwn["gitlab_get_workitem_notes"] s_cwn["gitlab_create_workitem_note"] s_wit["gitlab_get_work_item_types"] s_cmr["gitlab_create_merge_request"] s_gmr["gitlab_get_merge_request"] s_gmrc["gitlab_get_merge_request_commits"] s_gmrd["gitlab_get_merge_request_diffs"] s_gmrconf["gitlab_get_merge_request_conflicts"] s_gmrn["gitlab_get_merge_request_notes"] s_gmrp["gitlab_get_merge_request_pipelines"] s_cmrn["gitlab_create_merge_request_note"] s_mp["gitlab_manage_pipeline"] s_gpj["gitlab_get_pipeline_jobs"] s_gjl["gitlab_get_job_log"] s_search["gitlab_search"] s_labels["gitlab_search_labels"] end subgraph TGT["Consolidated target surface"] t_gwi["get_work_item (include: notes)"] t_wwi["save_work_item (create/update by work_item_iid presence)"] t_lwit["list_work_item_types (renamed from get_work_item_types)"] t_gmr["get_merge_request (include: diffs, commits, notes, pipelines, conflicts, discussions)"] t_lmr["list_merge_requests"] t_wmr["save_merge_request (create/update by merge_request_iid presence)"] t_wmrr["save_merge_request_review (method: reply/resolve/note/diff_note/submit/duo)"] t_gp["get_pipeline (include: jobs, downstream, bridge; job_status)"] t_lp["list_pipelines"] t_mp["save_pipeline (create; retry/cancel via action)"] t_gj["get_job (include: log)"] t_srch["search (scope + labels)"] end %% Work items / issues s_ci -->|"create (no iid)"| t_wwi s_gi --> t_gwi s_gwn -->|include=notes| t_gwi s_cwn --> t_wwi s_wit -->|rename| t_lwit %% Merge requests s_cmr --> t_wmr s_gmr --> t_gmr s_gmrc -->|include=commits| t_gmr s_gmrd -->|include=diffs| t_gmr s_gmrconf -->|include=conflicts| t_gmr s_gmrn -->|include=notes| t_gmr s_gmrp -->|include=pipelines| t_gmr s_cmrn --> t_wmrr %% Pipelines / CI s_mp -->|"create; action retry/cancel"| t_mp s_mp -->|list| t_lp s_gpj -->|include=jobs| t_gp s_gjl -->|include=log| t_gj %% Search s_search --> t_srch s_labels -->|scope=labels| t_srch subgraph OUT["Not consolidated (kept as-is / out of scope)"] o_link["gitlab_link_work_items"] o_saved["gitlab_get_saved_view_work_items"] o_ver["gitlab_get_mcp_server_version"] o_semantic["gitlab_semantic_code_search"] end ``` **How the 22 current tools map:** - **Merge request reads** — six tools (`get_merge_request` + `_commits`/`_diffs`/`_conflicts`/`_notes`/`_pipelines`) fold into one facet reader `get_merge_request` via `include`. - **Merge request writes** — `create_merge_request` → `save_merge_request`; `create_merge_request_note` → `save_merge_request_review`. - **Work items / issues** — `get_issue` + `get_workitem_notes` → `get_work_item` (`include: notes`); `create_issue` → `save_work_item`; `create_workitem_note` → `save_work_item_note`; `get_work_item_types` → `list_work_item_types` (rename to the `list_` verb class). - **Pipelines / CI** — `manage_pipeline` splits into lifecycle (`save_pipeline`) + `list_pipelines`; `get_pipeline_jobs` → `get_pipeline` (`include: jobs`); `get_job_log` → `get_job` (`include: log`). - **Search** — `gitlab_search` and `gitlab_search_labels` (via `scope=labels`) converge into one `search` tool; `gitlab_semantic_code_search` stays distinct for now. - **Not consolidated** — `link_work_items`, `get_saved_view_work_items`, `get_mcp_server_version`, and `semantic_code_search` stay as-is (utility/relationship tools and distinct search corpora outside the read/write/facet pattern).