Open
Conversation
|
|
- Add MCPMetadata struct (title, description, readOnlyHint, destructiveHint, idempotentHint, openWorldHint, tags) to api/v1/ - Add MCP field to PlaybookSpec and ViewSpec - Apply MCP annotations when registering playbook/view tools - Include identity metadata (title, description, category, icon, namespace, tags) in playbook and view list tool responses - Regenerate deepcopy, CRD manifests, and JSON schemas Co-authored-by: moshloop <1489660+moshloop@users.noreply.github.com>
Co-authored-by: moshloop <1489660+moshloop@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add MCP metadata to playbooks and views
Add MCP metadata to Playbook and View CRDs
Mar 19, 2026
Member
|
@copilot regen the resources using |
Contributor
Author
moshloop
added a commit
that referenced
this pull request
Apr 1, 2026
Add MCPMetadata struct with annotation hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) and tags for LLM tool discovery. Playbook and view tool registration now propagates these hints and supports title/description overrides. Incorporates #2896
moshloop
added a commit
that referenced
this pull request
Apr 1, 2026
Add MCPMetadata struct with annotation hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) and tags for LLM tool discovery. Playbook and view tool registration now propagates these hints and supports title/description overrides. Incorporates #2896
moshloop
added a commit
that referenced
this pull request
Apr 3, 2026
Add MCPMetadata struct with annotation hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) and tags for LLM tool discovery. Playbook and view tool registration now propagates these hints and supports title/description overrides. Incorporates #2896
moshloop
added a commit
that referenced
this pull request
Apr 3, 2026
Add MCPMetadata struct with annotation hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) and tags for LLM tool discovery. Playbook and view tool registration now propagates these hints and supports title/description overrides. Incorporates #2896
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
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.
Playbook and View MCP tools lack structured metadata for LLM clients. Tool listings return minimal info (id/name only), and there's no way to configure MCP annotation hints (readOnly, destructive, idempotent, openWorld) from CRD specs.
New
MCPMetadatatype (api/v1/mcp_metadata.go)Added to both
PlaybookSpecandViewSpecas an optionalmcpfield:Fields:
title,description,readOnlyHint,destructiveHint,idempotentHint,openWorldHint,tags.MCP tool registration
mcp.title/mcp.descriptionoverride spec defaults when setRicher list tool responses
get_all_playbooks: now returnstitle,namespace,description,category,icon,tags(previously onlyid+name)list_all_views: now returnstitle,namespace,description,icon,tags(previously only tool name strings)Generated files
CRD manifests, JSON schemas, and deepcopy functions regenerated via
make manifestsandmake generate.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.