Handle integer input

[olaservo]

Motivation and Context

Addresses this issue: #154

When the JSON schema specifies an integer, the current implementation displays a text field and ends up sending the input as a string, which isn't compliant with the JSON spec.

Changes made:

1. Integer Field Handling

   • Added integer input field with type="number" step="1"
   • Convert string values to numbers using Number() with validation
   • Ensures only valid integers are passed to the MCP server

2. Form Field Improvements

   • Added support for optional fields (undefined values)
   • Added proper handling of required fields
   • Added support for default values from schema
   • Improved null type handling

3. Value Generation

   • Updated default value generation to only generate default values for required fields
   • Handles undefined and null states

4. Array and Object Handling

   • Improved array item generation
   • Better handling of nested object properties
   • More robust JSON value type definitions

How Has This Been Tested?

I am still testing this with a real example of a schema with integer type. Will take this out of draft once tested.

Breaking Changes

No

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

[olaservo]

Closing to add tweaks to this PR instead: #159