mcp: add developer endpoint instructions for ontology-guided queries

[bobbyiliev]

As discussed here

[github-actions]

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

• Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
• Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
• Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

• The PR title is descriptive and will make sense in the git log.
• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).

[mtabebe]

This is great! A few questions/comments

1. I don't think we can actually merge now, because these tables don't exist. And if they do they will likely not have the mz_ name for now (as we aren't sure if we are going to use built in tables for now).
2. If I have more detailed prompts, what is the best way to load that as context (https://github.com/MaterializeInc/materialize/pull/36051/changes#diff-a96642aa1a069c9e0c155c6169b5398b9d4a3c55205918c6ce17318b76439c96) That is is there a way to give the MCP server the MD files?

In the meantime, I'm going to cherry pick this change locally for testing!

Thanks for the fast turn around!!