fix: fix the schema for embeddings parameter MCP-281

[himanshusinghs]

Proposed changes

This PR updates the schema of embeddingsParameters to expect a union on stringified numbers instead of numbers because OpenAPI JSON Schema supports enum of string only.

Checklist

• I have signed the MongoDB CLA

[Copilot]

Pull request overview

This PR fixes the schema for embedding parameters to ensure compatibility with OpenAPI JSON Schema requirements. The change addresses the limitation that OpenAPI JSON Schema only supports enum values as strings, not numbers.

Key Changes:

• Updated outputDimension schema to accept stringified numbers ("256", "512", etc.) instead of numeric literals
• Added transformation logic to parse string values back to numbers for internal use
• Updated all test cases to use stringified dimension values

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/tools/mongodb/mongodbSchemas.ts	Modified schema definitions to accept stringified numbers for outputDimension with transformation logic, and separated API parameters schema to maintain numeric types internally
tests/integration/tools/mongodb/read/aggregate.test.ts	Updated all test cases to use stringified outputDimension values ("256" instead of 256)
tests/integration/tools/mongodb/create/insertMany.test.ts	Updated test cases and commented code to use stringified outputDimension values

[Copilot]

The default value should be applied before the transformation, not after. The .default() should come before .transform() to provide the default string value that will then be transformed to a number. Current order means the default is applied after transformation, which expects a number but receives a string.

[himanshusinghs]

@gagik do you know if the order of function application is relevant here?

[himanshusinghs]

I tried using the schema as is on its own and it seemed to work fine.

[coveralls]

Pull Request Test Coverage Report for Build 19708808618

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 8 of 8 (100.0%) changed or added relevant lines in 1 file are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.02%) to 80.182%

---

Files with Coverage Reduction	New Missed Lines	%
src/tools/atlas/connect/connectCluster.ts	2	79.15%

Totals
Change from base Build 19701626410:	-0.02%
Covered Lines:	6475
Relevant Lines:	7982

---

💛 - Coveralls