fix: add min and max constraints on limit parameter in getCollections schema to avoid API Drift with underlying API implementation #59
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
… schema
The input schema of the getCollections tool was missing min and max constraints on the `limit` parameter. This fix aligns the schema with the actual API implementation to avoid drift between the API and MCP. Else we get the following error:
{type=text, text=MCP error -32602: API request failed: 400 {"error":{"name":"invalidParamsError","message":"The limit parameter provided is invalid. Value must be a positive integer smaller than 100.","details":{"param":"limit"}}}}
nashjain
requested review from
akinard-postman,
akira28,
alexander-rubia,
garciasdos and
rubenbaraut
as code owners
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.
The input schema of the
getCollectionstool was missing min and max constraints on thelimitparameter. This fix aligns the schema with the actual API implementation to avoid drift between the API and MCP.More details #58