docs: use Responses API in README MCP examples#436
Open
mvanhorn wants to merge 1 commit into
Open
Conversation
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.
What
Updates the README's Remote MCP examples to use the Responses API (
CreateModelResponseQuery+openAI.responses.createResponse) instead ofChatQuery, and adds a note that MCP tools are a Responses API feature not supported by Chat Completions.Why
The current MCP examples don't compile:
Tool.mcpToolonly fits the Responses API'stoolsparameter, whileChatQuery.toolsaccepts function tools only, so copying the README snippet produces a type error (#389). The corrected snippets compile against currentmain.Affected Areas
README.md only. No library code changes.
Fixes #389