MCP: optional deployment-platform filter for ask_redpanda_question - #197
Open
JakeSCahill wants to merge 1 commit into
Open
MCP: optional deployment-platform filter for ask_redpanda_question#197JakeSCahill wants to merge 1 commit into
JakeSCahill wants to merge 1 commit into
Conversation
Kapa search is plain semantic retrieval over the whole docs corpus, so a
broker-level question from a cloud user comes back dominated by
self-managed (/streaming/) sections, and downstream LLMs answer from the
wrong platform's docs. The docs are cleanly segmented by URL path, so
when the caller knows the deployment platform we can drop the other
platform's sections and keep everything neutral (Connect, API, labs,
external sources).
Adds an optional 'platform' param ('cloud' | 'self-managed') to
ask_redpanda_question, filters both the initial call and the retry, and
passes unexpected payload shapes through untouched. Bumps the server to
1.2.0.
✅ Deploy Preview for redpanda-documentation ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The CS Slack bot answered a BYOC customer's metrics question with self-managed instructions (
redpanda-cluster.yamledits) even though it knew the account's entitlement. Root cause: it passes the product type into the search query as text, but Kapa retrieval is plain semantic search over the whole corpus — for broker-level topics the self-managed pages dominate the results, and the LLM answers from them. Reproduced directly: "how do I enable a broker metric?" returns 13/15/streaming/sections, including the exact wrong-platform yaml the bot quoted.The docs are already segmented by URL path (
/streaming/= Self-Managed,/cloud-data-platform/= Cloud, everything else platform-neutral), so this adds an optionalplatformparameter (cloud|self-managed) toask_redpanda_questionthat drops the other platform's sections after retrieval. Neutral docs (Connect, API reference, labs, external sources) are always kept, and unexpected payloads (errors, upstream shape changes) pass through untouched. No behavior change when the param is omitted.Tested with
npx vitest run platform-filter.test.ts(7 tests). Pairs with the redsquadron-side change in internal-agents that applies the same filter in the bot's pipeline.