fix: correct the URL paths for accessing MCP endpoints#82
Open
ChristopheGigax-Microsoft wants to merge 2 commits into
Open
fix: correct the URL paths for accessing MCP endpoints#82ChristopheGigax-Microsoft wants to merge 2 commits into
ChristopheGigax-Microsoft wants to merge 2 commits into
Conversation
Author
|
@microsoft-github-policy-service agree company="Microsoft" |
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.
This pull request makes improvements to the integration and configuration of the machine knowledge base within the fault diagnosis agent. The main changes ensure the correct endpoint formatting for the knowledge base MCP connection and add a new tool for accessing the machine wiki knowledge base.
Endpoint configuration fixes:
machine_wiki_mcp_endpointURL in bothfault_diagnosis_agent.pyandcreate_knowledge_base.ipynbby adding a missing slash after the search endpoint, ensuring valid API requests. [1] [2]