Feature: store toolname for tool matching condition#97
Merged
mvle merged 3 commits intokagenti:mainfrom Apr 15, 2026
Merged
Conversation
Signed-off-by: mvle <[email protected]>
Signed-off-by: mvle <[email protected]>
Signed-off-by: mvle <[email protected]>
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.
Summary
Need the toolname for tool match condition.
MCP responses do not contain the toolname.
Added code to store toolname from request body phase. This is the phase where the toolname contains the prefix needed for tool condition matching. The toolname is then used only in the response body processing for tool matching condition.
Updated config.yaml to include toolname condition option used for matching.
Related issue(s)
(Optional) Testing Instructions
Fixes #37