Changes made to the MCP tool registration service#186
Open
Koolsiddude wants to merge 4 commits intomicrosoft:mainfrom
Open
Changes made to the MCP tool registration service#186Koolsiddude wants to merge 4 commits intomicrosoft:mainfrom
Koolsiddude wants to merge 4 commits intomicrosoft:mainfrom
Conversation
Author
|
@microsoft-github-policy-service agree |
nikhilNava
previously approved these changes
Mar 2, 2026
Contributor
nikhilNava
left a comment
There was a problem hiding this comment.
Update the dependency to the latest on the root *.toml file
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
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
This PR updates Agent Framework integration code to align with the latest Python API changes where chat message store abstractions were replaced by history providers and several import/parameter names were normalized.
Why this change
ChatMessageStoreProtocolis no longer available in newer Agent Framework releases, and some API parameter/import names have changed (includingchat_clienttoclient). Without this migration, imports and chat-history forwarding code can fail at runtime.What changed
1) Import migration
ChatMessageStoreProtocolimport withBaseHistoryProvider.2) Method signature migration
send_chat_history_from_store(...)to accept:history_provider: BaseHistoryProvidersession_id: Optional[str] = None3) Message retrieval migration
await chat_message_store.list_messages()history_provider.get_messages(session_id=session_id)4) Validation/messages/docs alignment
chat_message_storetohistory_provider.5) Additional import/parameter rename alignment
agentandmessagewhere required by updated signatures/types.chat_clientreferences toclient.File changed
libraries\microsoft-agents-a365-tooling-extensions-agentframework\microsoft_agents_a365\tooling\extensions\agentframework\services\mcp_tool_registration_service.pyBackward compatibility notes
BaseHistoryProviderand optionalsession_id.chat_client) must be updated to the current names (for exampleclient).Validation performed
microsoft_agents_a365.tooling.extensions.agentframework.services.mcp_tool_registration_serviceRisk assessment
Suggested reviewer checklist
BaseHistoryProvideris the intended abstraction for current Agent Framework version.session_idpropagation is correct for your session model.agent,message,chat_client) where newer names/signatures are expected.