feat: add specs for tools-scopes support#37
Open
rafaelsilva29 wants to merge 1 commit into
Open
Conversation
rafaelsilva29
requested review from
ChiaraTroiani,
beryder,
copasseron,
hmuyal,
jadiaconu,
mayannuz,
melhelou-cisco and
mkedjour
as code owners
rafaelsilva29
force-pushed
the
feat/add-specs-tools-scopes-support
branch
3 times, most recently
from
4944bd0 to
165f230
Compare
Signed-off-by: Rafael Silva (rafaelsi) <rafaelsi@cisco.com>
rafaelsilva29
force-pushed
the
feat/add-specs-tools-scopes-support
branch
from
f5856ba to
79a9eeb
Compare
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.
Description
Adds automatic MCP tool discovery on MultiAgentSystem CRD registration. When an mcp_server app is registered, CASA connects to its Streamable HTTP endpoint, lists tools and resources via the MCP SDK, and persists them to the Tool table — populating the previously empty tool catalog in the DB.
This is the foundation for per-tool token verification: docs/dev/specs/MCP_TOOL_TOKEN_VERIFICATION.md
Type of Change
Checklist