Problem Statement/Rationale

Sometimes, when using the /query command to build a query, and then at some point using the /schema to get information about the schema of a collection without opening a new chat window, Copilot keeps thinking that a user wants to build a query.

What might happen is that the model becomes confused by the previous context and not very clear prompt for the /schema command. we probably should update the prompt to specify what output we expect from this command. like not a runnable playground based on the previous conversation, but json schema.

The related Slack thread: https://mongodb.slack.com/archives/GTTUKDWRH/p1731575160161789

Steps to Reproduce

See the attached screenshot.

Expected Results

The /schema command returns a json schema of the collection

Actual Results

The /schema command generates a code block like the /query command