Initial Tools Selection for Remote MCP Server

Context

In #554828 (closed), API team has begun implementing Tools DSL for listing and calling tools included as part of !198243 (merged).

Right now, the initial tools are limited to getting context about the MCP server version and current user. While these basic tools are useful for testing end-to-end integration with MCP clients, these are not considered valuable workflows.

What

Engineering needs Product to select which GitLab REST API endpoints to expose as MCP tools beyond the basic context tools.

Why

• Current tools (version/user info) don't demonstrate real workflow value
• MCP protocol has practical limits on number of tools it can effectively handle
• Need versatile endpoints that enable various workflows rather than single-purpose operations

Constraints

• Must use existing REST API endpoints: https://docs.gitlab.com/api/api_resources/
• MCP cannot handle large numbers of tools effectively - need focused selection
• Limited implementation window for 18.3 milestone requires strategic product choices