Fix fundamental schema issue with required fields defined incorrectly on JsonSchemaType

[olaservo]

Fixes a critical schema architecture problem identified by @max-stytch where the JsonSchemaType definition violated the JSON Schema specification. JsonSchemaType incorrectly defined required as boolean on individual properties instead of string[] array on parent object schema, leading to unexpected behavior in some tools testing scenarios and several open issues.

Motivation and Context

Related observed issues:

• Issue Empty string parameters are not sent (validation error missing required argument) #406: Empty string parameters incorrectly converted to null/undefined
• Multiple form validation failures across ToolsTab and DynamicJsonForm components
• Broken prop.required logic throughout the codebase

How Has This Been Tested?

Did some basic testing but still working on more methodically testing the different scenarios. Thought it would be worth opening now for visibility's sake.

Breaking Changes

Technically yes due to internal API changes, however these all restore the correct behavior behind the scenes and don't require any changes on the user side:

• generateDefaultValue() function signature changed to include propertyName and parentSchema parameters
• JsonSchemaType.required changed from boolean to string[]
• Components using prop.required logic needed updates

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

[cliffhall]

Found a couple of places where isPropertyRequired helper can be used.

[pcarleton]

Auth debugger changes lgtm!

[cliffhall]

Do we have a goto in-project example, in the SDK or servers repo that could be used to exercise the various schema-related stuff like required fields and nested fields in input and output schemas?

[max-stytch]

Do we have a goto in-project example, in the SDK or servers repo that could be used to exercise the various schema-related stuff like required fields and nested fields in input and output schemas?

I want to put together a little Cloudflare Worker that can take in a generic tool schema and then generate an unauthenticated MCP Server URL that we can share for testing purposes. Just haven't had the time 😢

[cliffhall]

Do we have a goto in-project example, in the SDK or servers repo that could be used to exercise the various schema-related stuff like required fields and nested fields in input and output schemas?

I want to put together a little Cloudflare Worker that can take in a generic tool schema and then generate an unauthenticated MCP Server URL that we can share for testing purposes. Just haven't had the time 😢

That's cool and useful, and don't want to dissuade you from doing so. But I'm mainly looking for in-project stuff that we maintain with no external dependencies.