feat: expose metadata/datasets as an MCP-App-only tool for the UI widget#540
Open
kryachkow wants to merge 2 commits into
Open
Conversation
…get #533 Add a DatasetsMetadataApp tool that returns the channel's datasets metadata payload (matching the /metadata/datasets service endpoint) as MCP structured content so the UI widget can render it. The tool is MCP-only and app-only by default, keeping it hidden from the Supreme Agent. Extract the payload building into a shared build_channel_datasets_metadata service so the service endpoint and the new tool stay in sync.
…-app-only-tool-for-the-ui-widget
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.
Applicable issues
/metadata/datasetsas an MCP-App-only tool for the UI Widget #533Description of changes
Adds a new
DatasetsMetadataApptool that returns the channel's datasets metadata payload (the same payload as the/metadata/datasetsservice endpoint) so the UI widget can consume it through MCP.DatasetsMetadataAppToolchain that builds the response and returns it as aDatasetsMetadataAppArtifact.mcp_only=True, pinned) and app-only by default (mcp_visibility=["app"]), so it stays hidden from the Supreme Agent / model, which does not need dataset metadata through this path.build_channel_datasets_metadataservice so the service endpoint and the new tool stay in sync.DATASETS_METADATA_APP) in the enums, tool config, and channel config.Checklist
Reviewenvironment.By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.