add mcp-tef tool similarity check workflow [CLAUDE]#323
Open
jaylonmcshan19-x wants to merge 4 commits into
Open
add mcp-tef tool similarity check workflow [CLAUDE]#323jaylonmcshan19-x wants to merge 4 commits into
jaylonmcshan19-x wants to merge 4 commits into
Conversation
Changelog WarningPlease add a changelog entry to |
jaylonmcshan19-x
changed the title
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
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
2 participants
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.
PCI review checklist
This PR adds a GHA workflow that checks tool description similarity on PRs touching
pkg/tools/**. This helps catch tool descriptions that are too similar and could confuse LLMs during tool selection.Claude helped with creating the summary table
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.