Improve Slash-Command UI for MCP Prompts

[pattobrien]

Feature Enhancement Description

After using VSCode's latest MCP implementation with my own custom MCP Server (which implements MCP Prompts primitives), I have some usability suggestions for UI improvements when using slash commands to view available MCP prompts:

• use a shorter Prompt reference so that the available prompts are easier to grok
  • and/or use the Prompt name property on the right hand side of the list item (currently shows the Prompt description instead)
• show the Prompt description when hovering on a prompt item (as is done with built-in slash commands)
  • currently shows nothing when hovering the item

I figured that since these suggestions are related to the same view, a single issue would do - but please let me know if you'd like me to create multiple issues.

Current Behavior

Example of Built-In Slash Commands (which look much better)

[iwangbowen]

The feature need to be polished

[connor4312]

@hawkticehurst any suggestions for design for this? 🙂

[hawkticehurst]

@connor4312 I do, that's why I left myself as assigned to the issue 😉 I'll ponder on it tonight and come back with thoughts tomorrow

[hawkticehurst]

Hi! Sorry for delay (took a sick day yesterday), but I actually think we can just be wicked simple here and copy the overall format of built-in slash commands do (just like the example that @pattobrien shared).

Core changes:

• Left side of slash command context menu contains just the MCP prompt name
• Right side of slash command context menu contains the MCP server name
• Hover tooltip contains the prompt description

Remaining open questions:

• Should we be more clear that these are from an MCP server or does it not matter? I'm leaning towards we don't necessarily need to be clear that this is from an MCP, it's just one command/prompt amongst others
• Do we need to include an @ symbol in front of mcp server names? I think no because @ is reserved for chat participants right?
• Do we need to indicate that a prompt is dynamic / has arguments or is it fine to just let whether a prompt is dynamic / has arguments once it's been selected?