Skip to content

fix(mcp): accept whole-number float maxResults from MCP clients#328

Open
Jah-yee wants to merge 1 commit intodmtrKovalenko:mainfrom
Jah-yee:fix/maxresults-float
Open

fix(mcp): accept whole-number float maxResults from MCP clients#328
Jah-yee wants to merge 1 commit intodmtrKovalenko:mainfrom
Jah-yee:fix/maxresults-float

Conversation

@Jah-yee
Copy link
Copy Markdown

@Jah-yee Jah-yee commented Apr 3, 2026

Good day

Some MCP clients serialize integer values as floats (e.g., 30.0 instead of 30).
This change allows the MCP server to accept both usize and whole-number f64
values for the maxResults parameter, while rejecting fractional values.

Fixes issue #326

感谢你们的奉献,希望能提供帮助。如果我解决得有问题或有待商妥的地方,请在下面留言,我会来处理。

Warmly,

Some MCP clients serialize integer values as floats (e.g., 30.0 instead of 30).
This change allows the MCP server to accept both usize and whole-number f64
values for the maxResults parameter, while rejecting fractional values.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant