Unique tool desc created in mcp tools to allow multiple tool integrations. #11
Conversation
This file contains 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.
If someone can just create an api call in rememberizer to allow the CK description to be called, we can swap that call result with the process_id. Allow a couple lines of space. And then suddenly our tools can appear uniquely in a Claude or SD session and the LLM can tell the difference between one tool and the other and know when, why, and if to call any particular instance of a tool/rememberizer integration. So this allows multiple rememberizer integrations to multiple different Common Knowledges for different purposes.
This is more of a proof of concept than a completed solution because we need these extra steps.