EPIC Goal

Provide more information on MCP tool usage in Developer Lightspeed, along with what tools are available

Background/Feature Origin

As part of RHDHPLAN-43 and RHDHPLAN-31 , we delivered on providing support MCP tools in RHDH, including calling Backstage MCP tools from within Developer Lightspeed.

Following up on that, we would like for the Lightspeed UI to provide further information on the MCP tool trails (which tools were called, and from which servers), and display which tools are available (note: tool selection is considered stretch)

Why is this important?

This will provide more clarity on which MCP tools are available to the user, and which MCP tools are called by the model, allowing users to be more informed about the decisions made by Developer Lightspeed.

Scope

• MCP tool availability (which tools are available)
• Stretch: MCP tool selection

Dependencies (internal and external)

Acceptance Criteria

• Developer Lightspeed shows which tools are available

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>